public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Miner <mine0057@mrs.umn.edu>
To: linux-kernel@vger.kernel.org
Cc: reiserfs-list@namesys.com
Subject: Filesystem Tests
Date: Tue, 05 Aug 2003 21:30:48 -0500	[thread overview]
Message-ID: <3F306858.1040202@mrs.umn.edu> (raw)

I tested the performace of various filesystems with a mozilla build tree 
of 295MB, with primarily writing and copying operations.  The test 
system is Linux 2.6.0-test2, 512MB memory, 11531.85MB partition for 
tests.  Sync is run a few times throughout the test (for full script see 
bottom of this email).  I ran mkfs on the partition before every test. 
Running the tests again tends to produces similar times, about +/- 3 
seconds.

The first item number is time, in seconds, to complete the test (lower 
is better).  The second number is CPU use percentage (lower is better).

reiser4 171.28s, 30%CPU (1.0000x time; 1.0x CPU)
reiserfs 302.53s, 16%CPU (1.7663x time; 0.53x CPU)
ext3 319.71s, 11%CPU	(1.8666x time; 0.36x CPU)
xfs 429.79s, 13%CPU (2.5093x time; 0.43x CPU)
jfs 470.88s, 6%CPU (2.7492x time 0.02x CPU)

What's interesting:
* ext3's syncs tended to take the longest 10 seconds, except
* JFS took a whopping 38.18s on its final sync
* xfs used more CPU than ext3 but was slower than ext3
* reiser4 had highest throughput and most CPU usage
* jfs had lowest throughput and least CPU usage
* total performance of course depends on how IO or CPU bound your task is

Individual test times (first number again is time in seconds, second is 
CPU usage, last is total again)
reiser4
Copying Tree
33.39,34%
Sync
1.54,0%
recopying tree to mozilla-2
31.09,34%
recopying mozilla-2 to mozilla-3
33.15,33%
sync
2.89,3%
du
2.05,42%
rm -rf mozilla
7.41,52%
tar c mozilla-2
52.25,25%
final sync
6.77,2%
171.28,30%

reiserfs
Copying Tree
39.55,32%
Sync
3.15,1%
recopying tree to mozilla-2
75.15,13%
recopying mozilla-2 to mozilla-3
77.62,13%
sync
3.84,1%
du
2.46,21%
rm -rf mozilla
5.22,58%
tar c mozilla-2
90.83,12%
final sync
4.19,3%
302.53,16%

extended 3
Copying Tree
39.42,25%
Sync
9.05,0%
recopying tree to mozilla-2
79.96,9%
recopying mozilla-2 to mozilla-3
98.84,7%
sync
8.15,0%
du
3.31,11%
rm -rf mozilla
3.71,39%
tar c mozilla-2
74.93,13%
final sync
1.67,1%
319.71,11%

xfs
Copying Tree
43.50,32%
Sync
2.08,1%
recopying tree to mozilla-2
102.37,12%
recopying mozilla-2 to mozilla-3
108.00,12%
sync
2.40,2%
du
3.73,32%
rm -rf mozilla
8.75,56%
tar c mozilla-2
157.61,7%
final sync
0.95,1%
429.79,13%

jfs
Copying Tree
48.15,20%
Sync
3.05,1%
recopying tree to mozilla-2
108.39,5%
recopying mozilla-2 to mozilla-3
114.96,5%
sync
3.86,0%
du
2.42,17%
rm -rf mozilla
15.33,7%
tar c mozilla-2
135.86,6%
final sync
38.18,0%
470.88,6%

Here is the benchmark script:
#!/bin/sh
time='time -f%e,%P '
echo "Copying Tree"
$time cp -a /home/test/mozilla /mnt/test
echo "Sync"
$time sync
cd /mnt/test &&
echo "recopying tree to mozilla-2"
$time cp -a mozilla mozilla-2 &&
echo "recopying mozilla-2 to mozilla-3"
$time cp -a mozilla mozilla-2 &&
echo "sync"
$time sync &&
echo "du"
$time du mozilla > /dev/null &&
echo "rm -rf mozilla"
$time rm -rf mozilla
echo "tar c mozilla-2"
$time tar c mozilla-2 > mozilla.tar
echo "final sync"
$time sync


             reply	other threads:[~2003-08-06  2:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  2:30 Grant Miner [this message]
2003-08-06  3:47 ` Filesystem Tests Peter Chubb
2003-08-06 10:43   ` Oleg Drokin
2003-08-06  5:41 ` Andrew Morton
2003-08-06 10:35   ` Szakacsits Szabolcs
2003-08-09  1:09     ` Jamie Lokier
2003-08-09  5:12       ` Szakacsits Szabolcs
2003-08-09  9:33         ` Jamie Lokier
2003-08-09  9:18           ` Szakacsits Szabolcs
2003-08-09 16:19             ` Jamie Lokier
2003-08-10 21:03               ` Grant Miner
2003-08-12  8:27                 ` Dieter Nützel
2003-08-06 14:06   ` Hans Reiser
2003-08-06 16:34     ` Diego Calleja García
2003-08-06 18:04       ` Mike Fedyk
2003-08-06 18:45         ` Diego Calleja García
2003-08-06 19:08           ` Mike Fedyk
2003-08-06 19:40             ` Diego Calleja García
2003-08-07 13:51               ` Hans Reiser
2003-08-07  0:55           ` Clemens Schwaighofer
2003-08-06 21:19         ` Andrew Morton
2003-08-06 21:25           ` ieee1394 (Firewire) driver problem Henrik Raeder Clausen
2003-08-07 12:55       ` Filesystem Tests Hans Reiser
2003-08-07 19:09         ` Diego Calleja García
2003-08-07 19:21           ` ahorn
2003-08-06 23:37     ` Timothy Miller
2003-08-06 23:47       ` Mike Fedyk
2003-08-07  0:40         ` Timothy Miller
2003-08-07 13:55     ` jlnance
2003-08-06  9:55 ` Felipe Alfaro Solana
2003-08-06 10:48 ` Paul Dickson
2003-08-06 11:39   ` Grant Miner

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=3F306858.1040202@mrs.umn.edu \
    --to=mine0057@mrs.umn.edu \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox