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:38:26 +0300 [thread overview]
Message-ID: <404E0112.7080904@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.58L0.0403091929530.9967@ahriman.bucharest.roedu.net>
Mihai RUSU wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Tue, 9 Mar 2004, Hans Reiser wrote:
>
>
>
>>>This one:
>>>62922 for v3 and 52469 for v4
>>>
>>>
>>>
>>>
>>what is the amount of ram vs. the amount written? If you write 10x the
>>ram, does the performance loss go away?
>>
>>
>
>bonnie++ writes by default in the "block" tests double of memory (so it
>makes sure the cache has a small impact). I have 512 mb of ram and the
>ammount of data written was 1gb. I can force it to write 10x ...
>considering what I said here do you still want that ?
>
>- --
>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)
>
>iD8DBQFATf+iPZzOzrZY/1QRAhIQAJ0W4Y7gvIMp0TnpXXXE9kubMgrr/wCePHCM
>LBpuALzT+Mun64EcyAMd4bc=
>=wQqP
>-----END PGP SIGNATURE-----
>
>
>
>
Yes, it would be interesting. I think maybe we need to tweak reiser4
more for benchmarks near to ram size.
--
Hans
next prev parent reply other threads:[~2004-03-09 17:38 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
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 [this message]
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=404E0112.7080904@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.