All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Mihai RUSU <dizzy@roedu.net>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfs v3 vs v4 bonnie++ benchmarks
Date: Tue, 09 Mar 2004 20:11:42 +0300	[thread overview]
Message-ID: <404DFACE.4090008@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.58L0.0403091811140.5982@ahriman.bucharest.roedu.net>

Mihai RUSU wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi
>
>Im playing with reiser4 lately and while doing this I have run some 
>bonnie++ tests on both v3 and v4 reiserfs, on the same machine.
>
>I have this interesting results (I have run the tests 3 times for each FS 
>but the results were almost the same):
>
>V3:
>Version  1.03       ------Sequential Output------ --Sequential Input- --Random-
>                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
>Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
>dizzywork        1G 13459  71 62922  20 26061   6 15687  83 54593   8 191.0   0
>                    ------Sequential Create------ --------Random Create--------
>                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>files:max:min        /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
>256:64000:16000/256  1287  27   165   2 11382  77  1230  25    63   1   253   2
>
>V4:
>Version  1.03       ------Sequential Output------ --Sequential Input- --Random-
>                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
>Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
>dizzywork        1G 16926  87 52469  15 26474  11 16759  85 55349   9 166.6   1
>                    ------Sequential Create------ --------Random Create--------
>                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>files:max:min        /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
>256:64000:16000/256   863  40  1243  16  4219  47   873  46    81   1  3980  48
>  
>

>Interesting issues:
>- - see that the "sequential writes" test using write with a 8192 bytes 
>  
>
which of the above is this, the sequential output test?

>buffer is lower with v4 than with v3 (and it was like that in all tests)
>- - both reiserfs v3 and v4 have almost same number of "little" files 
>created in both sequential or random order but... reiser4 is much slower 
>than v3 here
>  
>
are little files = 64k?

>- - different than v3, reiser4 has almost the same speed at deleting small 
>files in either random or sequential order but in the sequential case its 
>much slower than v3
>- - Im very glad to see the BIG speed increase in reading small files in 
>sequential order although I would love to see more increase in the random 
>order case (closer to real-life)
>  
>
I need to take the time to read through bonnie++ so that I can really 
understand it, sigh, not today...

It does seem clear though that V4 consumes too much CPU for creates and 
writes, and that we are CPU bound for this task.  After we release it 
Zam will tweak it more, and I will review the write code again.  He is 
tweaking the linux profiler to collect better statistics on parent callers.

Thanks for gathering this data.

>System information:
>- - P4 2ghz 512 kb cache 2 x 256 MB DDR 
>- - kernel 2.6.3 with reiser4 patch all.diff.gz downloaded today (from 
>LATEST dir)
>- - mkfs default options for both v3 and v4
>- - 40 gb single partition on a 40 gb IDE drive 
>hdparm -iv /dev/hdb
>
>/dev/hdb:
> multcount    = 16 (on)
> IO_support   =  3 (32-bit w/sync)
> unmaskirq    =  0 (off)
> using_dma    =  1 (on)
> keepsettings =  0 (off)
> readonly     =  0 (off)
> readahead    = 256 (on)
> geometry     = 65535/16/63, sectors = 78165360, start = 0
> 
>udma5, writecache enabled (8mb cache)
>
>- - kernel options :
>$ grep -i reiser .config
>CONFIG_REISER4_FS=y
># CONFIG_REISER4_FS_SYSCALL is not set
>CONFIG_REISER4_LARGE_KEY=y
># CONFIG_REISER4_CHECK is not set
>CONFIG_REISER4_USE_EFLUSH=y
># CONFIG_REISER4_COPY_ON_CAPTURE is not set
># CONFIG_REISER4_BADBLOCKS is not set
>CONFIG_REISERFS_FS=y
># CONFIG_REISERFS_CHECK is not set
># CONFIG_REISERFS_PROC_INFO is not set
>
>- -- 
>Mihai RUSU                                    Email: dizzy@roedu.net
>GPG : http://dizzy.roedu.net/dizzy-gpg.txt    WWW: http://dizzy.roedu.net
>                       "Linux is obsolete" -- AST
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFATfB5PZzOzrZY/1QRAnu5AJ9ZdGt9BE8iPz9iB/QrnzYOr2XIiwCcCgfb
>lY0VWu16eyCMiQceZP1d708=
>=l+SO
>-----END PGP SIGNATURE-----
>
>
>  
>


-- 
Hans



  reply	other threads:[~2004-03-09 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 16:27 reiserfs v3 vs v4 bonnie++ benchmarks Mihai RUSU
2004-03-09 17:11 ` Hans Reiser [this message]
2004-03-09 17:18   ` Mihai RUSU
2004-03-09 17:24     ` Hans Reiser
2004-03-09 17:32       ` Mihai RUSU
2004-03-09 17:38         ` Hans Reiser
2004-03-09 21:14           ` Mihai RUSU
2004-03-10  6:33             ` Hans Reiser
2004-03-11  8:33               ` Mihai RUSU
2004-03-25 23:35               ` Mike Fedyk

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=404DFACE.4090008@namesys.com \
    --to=reiser@namesys.com \
    --cc=dizzy@roedu.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.