| To: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Jfs-discussion] benchmark results |
| From: | tytso@xxxxxxx |
| Date: | Fri, 25 Dec 2009 11:14:53 -0500 |
| Cc: | Peter Grandi <pg_jf2@xxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, reiserfs-devel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, jfs-discussion@xxxxxxxxxxxxxxxxxxxxx, ext-users <ext3-users@xxxxxxxxxx>, linux-nilfs@xxxxxxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.2.01.0912241739160.3483@xxxxxxxxxxxxxxxxxx> |
| References: | <alpine.DEB.2.01.0912240205510.3483@xxxxxxxxxxxxxxxxxx> <19251.26403.762180.228181@xxxxxxxxxxxxxxxxxx> <20091224212756.GM21594@xxxxxxxxx> <alpine.DEB.2.01.0912241739160.3483@xxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
On Thu, Dec 24, 2009 at 05:52:34PM -0800, Christian Kujau wrote:
>
> Well, I do "sync" after each operation, so the data should be on disk, but
> that doesn't mean it'll clear the filesystem buffers - but this doesn't
> happen that often in the real world too. Also, all filesystem were tested
> equally (I hope), yet some filesystem perform better than another - even
> if all the content copied/tar'ed/removed would perfectly well fit into the
> machines RAM.
Did you include the "sync" in part of what you timed? Peter was quite
right --- the fact that the measured bandwidth in your "cp" test is
five times faster than the disk bandwidth as measured by hdparm, and
many file systems had exactly the same bandwidth, makes me very
suspicious that what was being measured was primarily memory bandwidth
--- and not very useful when trying to measure file system
performance.
- Ted
|
| Previous by Date: | Re: [Jfs-discussion] benchmark results, tytso |
|---|---|
| Next by Date: | Re: [Jfs-discussion] benchmark results, Larry McVoy |
| Previous by Thread: | Re: [Jfs-discussion] benchmark results, lakshmi pathi |
| Next by Thread: | Re: [Jfs-discussion] benchmark results, Larry McVoy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |