From: Brian Tinsley <btinsley@emageon.com>
To: Radim Kolar <hsn@cybermail.net>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: filesystem overhead on large files
Date: Mon, 12 Aug 2002 11:30:34 -0500 [thread overview]
Message-ID: <3D57E2AA.3080808@emageon.com> (raw)
In-Reply-To: 20020811103327.GA8189@home
We use ReiserFS to store and serve medical images, which can be anywhere
from 30KB to hundreds of MB. ReiserFS provided the most consistent and
most often the best performance versuses other viable Linux filesystems
(we tested ext2, ext3, and XFS - JFS was not mature enough at the time).
I can also attest to the fact that an Oracle database is *extremely*
fast when stored on a ReiserFS formatted filesystem.
Radim Kolar wrote:
>tests on 100 mb file on ide disk
>hdd: 6306048 sectors (3229 MB) w/81KiB Cache, CHS=6256/16/63, (U)DMA
>
>dt was using async io in this test
> ./dt of=/dev/hdd1 limit=100m bs=16k dispose=keep passes=10 errors=50
> enable=aio
>
>kernel 2.4.19
>=============
>
>Raw disk IO: /dev/hdd1
> read 2260674 bytes/sec
> write 3542486 bytes/sec
>
>reiserfs:
> read 2265559 bytes/sec
> write 3524625 bytes/sec
>ext2:
> read 2226276 bytes/sec
> write 3214847 bytes/sec
>ext3:
> read 2189094 bytes/sec
> write 3201759 bytes/sec
>minix:
> read 2208303 bytes/sec
> write 3046710 bytes/sec
>vfat:
> read 2159045 bytes/sec
> write 2573193 bytes/sec
>
>i do not have XFS there XFS claims to be filesystem with highest possible
>transfer rate on large files, but this test shows that reiserfs has
>almost zero overhead on large files, so it can be also multimedia fs.
>
>We are considering to use Oracle in raw disk mode (without filesystem)
>and this test shows that you will not get any benefit from that - and
>backup/restore procedure is more complicated.
>
--
Brian Tinsley
Chief Systems Engineer
Emageon
http://www.emageon.com/
prev parent reply other threads:[~2002-08-12 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 10:33 filesystem overhead on large files Radim Kolar
2002-08-12 16:30 ` Brian Tinsley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D57E2AA.3080808@emageon.com \
--to=btinsley@emageon.com \
--cc=hsn@cybermail.net \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.