From: Hans Reiser <reiser@namesys.com>
To: Grant Miner <mine0057@mrs.umn.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: r4 v. ext3, quick speed vs. cpu experiments
Date: Wed, 06 Aug 2003 03:46:28 +0400 [thread overview]
Message-ID: <3F3041D4.9050709@namesys.com> (raw)
In-Reply-To: <3F303DA4.306@mrs.umn.edu>
Grant Miner wrote:
> Szakacsits Szabolcs wrote:
>
>> How much memory you have? How big is mozilla-1.5a.tar? Did you include
>> 'sync' in the tests? It seems reiser4 numbers are mostly in-memory
>> operations and not all data flushed to disk while this is apparently not
>> true for ext3. BTW, XFS numbers would be also/more interesting,
>> ext[23] is
>> pretty outdated.
>>
>> BTW, from your numbers it seems ext3 gives better overall performance.
>>
>> Szaka
>>
> Good suggestion. With ext3, 'sync' adds 10.2 seconds average to total
> time (others about 1.6 sec). Here is a list of averages, including sync
> time. Each fs was run 3 times. Note that I did not count sync's cpu %
> in cpu %.
>
> xfs: average 44.3 seconds, 32% cpu
> ext3: average 44.0 seconds, 27% cpu
> r4: average 30.2 seconds, 39% cpu
>
> I have 512MB memory. File tree is about 295 MB. This was just a "for
> fun" test, and it probably not accurate. I may try better ones later.
>
>
>
>
Expect the CPU time to drop a lot, because we first got rid of the IO
consuming kruft, now we are getting rid of the CPU consuming kruft.
That is, expect it to drop up until we ship a compression plugin.....
Can you post your numbers on lkml also?
--
Hans
prev parent reply other threads:[~2003-08-05 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 22:06 r4 v. ext3, quick speed vs. cpu experiments Grant Miner
2003-08-05 21:08 ` Szakacsits Szabolcs
2003-08-05 22:49 ` Brandon Low
2003-08-05 21:35 ` Szakacsits Szabolcs
2003-08-05 23:04 ` Brandon Low
2003-08-06 20:30 ` Matthias Andree
2003-08-05 23:28 ` Grant Miner
2003-08-05 23:46 ` Hans Reiser [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=3F3041D4.9050709@namesys.com \
--to=reiser@namesys.com \
--cc=mine0057@mrs.umn.edu \
--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.