From: Hans Reiser <reiser@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: Dark Shadow <shadowofdarkness@gmail.com>, reiserfs-list@namesys.com
Subject: Re: Why is Reiser4 slower then ReiserFS v3
Date: Tue, 28 Dec 2004 13:34:47 -0800 [thread overview]
Message-ID: <41D1D177.4080800@namesys.com> (raw)
In-Reply-To: <200412272353.iBRNrUcv002561@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Mon, 27 Dec 2004 13:38:12 MST, Dark Shadow said:
>
>
>
>>I have three hard drives so I took a file from one and copied it to
>>the others and timed it
>>source drive /dev/hda Reiser3 Western Digital 40gb 7200rpm
>>target1 drive /dev/hdb Reiser4 Western Digital 80gb 7200rpm
>>target2 drive /dev/sda Reiser3 Seagate 160gb 7200rpm (SATA but still
>>same rpm as rest so it should be the same)
>>
>>
>
>You may wish to run 'hdparm -T -t' on each drive and see what the *raw* speed
>is. All drives are not created equal... ;)
>
>
This is correct. You should see negligible difference between the two
for large files on the same drive. Deletions however, see next email....
>>time cp ~/800mb.file /target1
>>real 0m41.409s
>>user 0m0.010s
>>sys 0m4.364s
>>
>>
>
>
>
>>time cp ~/800mb.file /target2
>>real 0m38.318s
>>user 0m0.017s
>>sys 0m5.627s
>>
>>
>
>Similarly, you should try each one 3-5 times and get an average (for
>starters, if you have more than 800M of memory, the second time around it
>may all still be in cache, so the second time gets a hot-cache boost). It
>may be useful to run the command once and *ignore* its times, and then
>re-run the command 3 times and average those results (so all 3 times you
>actually *use* start from the same "previous command just finished" cache state).
>
>
next prev parent reply other threads:[~2004-12-28 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 20:38 Why is Reiser4 slower then ReiserFS v3 Dark Shadow
2004-12-27 23:53 ` Valdis.Kletnieks
2004-12-28 21:34 ` Hans Reiser [this message]
2004-12-28 18:52 ` Adrian Ulrich
2004-12-28 21:42 ` Hans Reiser
2004-12-29 6:34 ` Adrian Ulrich
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=41D1D177.4080800@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=reiserfs-list@namesys.com \
--cc=shadowofdarkness@gmail.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.