Re: [reiserfs-list] CPU useage of ReiserFS

2001-07-08 Thread Hans Reiser

Jens Benecke wrote:
 
 Hi,
 
 I just had a, er, 'lively' discussion with someone claiming ReiserFS is
 crap because it hogs even the fastest CPU too much, and it uses 4x as much
 processing power to do metadata operations, and in general is slower
 because of the journal. My benchmarks don't reflect this, especially on
 current hardware (ATA-66 and ATA-100 disks on VIA chipsets).
 
 While I agree that the journal does create an additional overhead, I'd like
 to know if the CPU overhead is really that much. I've seen your benchmarks
 on the web site but they don't say anything about CPU useage.
 
 --
 Jens Benecke
 http://www.hitchhikers.de/ - Die kostenlose Mitfahrzentrale für ganz Europa
 
   

Part 1.2Type: application/pgp-signature

There is higher CPU overhead when using tails.  I don't know about what happens 
without tails, never
measured it.  If you use large directories, ext2 dies under CPU overload.

Hans



Re: [reiserfs-list] CPU useage of ReiserFS

2001-07-02 Thread Russell Coker

On Saturday 30 June 2001 20:29, Jens Benecke wrote:
 I just had a, er, 'lively' discussion with someone claiming ReiserFS is
 crap because it hogs even the fastest CPU too much, and it uses 4x as
 much processing power to do metadata operations, and in general is
 slower because of the journal. My benchmarks don't reflect this,
 especially on current hardware (ATA-66 and ATA-100 disks on VIA
 chipsets).

 While I agree that the journal does create an additional overhead, I'd
 like to know if the CPU overhead is really that much. I've seen your
 benchmarks on the web site but they don't say anything about CPU
 useage.

I agree with Craig, I have one thing to add that Craig missed.

Every 12 to 24 months CPU speed doubles.  Now 1.4GHz CPUs with advanced 
cache and memory architectures are common while in 1990 20MHz CPUs 
without any caches were where it was at.

Hard drive speed increases much more slowly.  Now typical seek times are 
around 5ms and transfer rates are 35MB/s.  In 1990 seek times were around 
24ms and transfer rates were around 1MB/s.

For future scalability a file system that uses lots of CPU time may be 
better than a file system that uses lots of disk access.

-- 
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/   Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page



Re: [reiserfs-list] CPU useage of ReiserFS

2001-06-30 Thread Jean-Francois Landry

On Sat, Jun 30, 2001 at 08:29:04PM +0200, Jens Benecke wrote:
 Hi,
 
 I just had a, er, 'lively' discussion with someone claiming ReiserFS is
 crap because it hogs even the fastest CPU too much, and it uses 4x as much
 processing power to do metadata operations, and in general is slower
 because of the journal. My benchmarks don't reflect this, especially on
 current hardware (ATA-66 and ATA-100 disks on VIA chipsets).
 
 While I agree that the journal does create an additional overhead, I'd like
 to know if the CPU overhead is really that much. I've seen your benchmarks
 on the web site but they don't say anything about CPU useage.

Here's what happens when I rm a big directory tree on ext2 and reiserfs:

ext2 -- Disk trashes like mad. Forget accessing it while rm is running.
CPU usage is relatively low.

Reiserfs -- Light disk accesses with little seeking (can barely hear it,
LED blinks softly). Can do light jobs on the disk while rm
is running. CPU usage hovers between 65% and 95%.

OK, all those B* trees suck CPU cycles, and the journal means overhead,
but in my humble opinion it's worth it. Even with the CPU hogging, most
IO operations seem snappier to me on Reiserfs (at least compared to
ext2, can't say about XFS or JFS). And I'm not even talking of the more
efficient file packing.

You makes your choices, you lives with it ;)

Jean-Francois Landry
-- 
In short, just as the Multics mentality of careful access controls
shows up throughout Unix, the cretinous CP/M mentality of uncontrolled
havoc shows up in DOS and all its mutant children.
 
--- Tom Christiansen
--



Re: [reiserfs-list] CPU useage of ReiserFS

2001-06-30 Thread Craig Sanders

On Sat, Jun 30, 2001 at 06:25:18PM -0400, Jean-Francois Landry wrote:

 On Sat, Jun 30, 2001 at 08:29:04PM +0200, Jens Benecke wrote:
  I just had a, er, 'lively' discussion with someone claiming ReiserFS
  is crap because it hogs even the fastest CPU too much, and it
  uses 4x as much processing power to do metadata operations, and
  in general is slower because of the journal. My benchmarks don't
  reflect this, especially on current hardware (ATA-66 and ATA-100
  disks on VIA chipsets).

it's not that important in many (most?) situations that require fast
file I/O.

the CPU in most I/O bound applications sits idle waiting for the disk.
probably the only place where it would really matter would be in a
beowulf style cluster or rendering farm. it's rare for any application
to do a lot of I/O *and* a lot of computation.

image files are huge, so a render-farm would be better off using XFS
than reiserfs anyway - all benchmarks i've seen (including my own bonnie
runs[1]) show that XFS is faster for large files, while reiserfs is much
faster for lots of little files. overall, reiserfs is faster, but XFS
uses less CPU.


for applications that are primarily CPU-bound, it probably doesn't make
much difference what file-system is used.

for applications that are primarily IO-bound, the best filesystem to use
depends on the nature of the application.

in any case, you have to carefully benchmark all the available
filesystems and weigh up the pros and cons until you've found the one
that works best with your application.

saying that reiserfs is best, or xfs is best, or foo-fs is best, is just
plain silly - every fs has advantages and disadvantages.


e.g. i'd use reiserfs for a mail queue fs or a news spool or Maildir/
style mail spools. for a mail spool with large mbox files, i'd use XFS.

if i had to choose one or the other, i'd probably choose
reiserfs...although it's a difficult choice: reiserfs wins overall on
performance, but XFS has had several years more debugging in real-world
conditions (on SGI's IRIX)

i guess all this is a long way of saying facts and figures are
relevant, but unsupported opinion counts for nothing.



[1] my preliminary benchmark results are at:
http://siva.taz.net.au/~cas/x-vs-r.html

this is only a benchmark of a single IBM 40GB drive.  I bought a pair of
these and had intended to also benchmark a software RAID-0 setup, but
one of the drives was faulty when it arrived (DMA and BAD CRC errors).
i'll do another bonnie run when the replacement arrives.


 OK, all those B* trees suck CPU cycles, and the journal means overhead,
 but in my humble opinion it's worth it. Even with the CPU hogging, most
 IO operations seem snappier to me on Reiserfs (at least compared to
 ext2, can't say about XFS or JFS). And I'm not even talking of the more
 efficient file packing.
 
 You makes your choices, you lives with it ;)

yep.

craig

--
Craig Sanders
Systems Administrator
VICNET- Victoria's Network  http://www.vicnet.net.au/