xfs
[Top] [All Lists]

Re: [Jfs-discussion] benchmark results

To: jim owens <jowens@xxxxxx>
Subject: Re: [Jfs-discussion] benchmark results
From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Date: Sat, 26 Dec 2009 11:06:38 -0800
Cc: Larry McVoy <lm@xxxxxxxxxxxx>, tytso@xxxxxxx, jfs-discussion@xxxxxxxxxxxxxxxxxxxxx, linux-nilfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, reiserfs-devel@xxxxxxxxxxxxxxx, Peter Grandi <pg_jf2@xxxxxxxxxxxxxxxxxx>, ext-users <ext3-users@xxxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx
In-reply-to: <4B36333B.3030600@xxxxxx>
References: <alpine.DEB.2.01.0912240205510.3483@xxxxxxxxxxxxxxxxxx> <19251.26403.762180.228181@xxxxxxxxxxxxxxxxxx> <20091224212756.GM21594@xxxxxxxxx> <alpine.DEB.2.01.0912241739160.3483@xxxxxxxxxxxxxxxxxx> <20091225161453.GD32757@xxxxxxxxx> <20091225162238.GB19303@xxxxxxxxxxxx> <alpine.DEB.2.01.0912251042540.3483@xxxxxxxxxxxxxxxxxx> <4B36333B.3030600@xxxxxx>
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0
On 26.12.09 08:00, jim owens wrote:
>> I was using "sync" to make sure that the data "should" be on the disks 
> 
> Good, but not good enough for many tests... info sync
[...]
>        On Linux, sync is only guaranteed to  schedule  the  dirty  blocks  for
>        writing;  it  can  actually take a short time before all the blocks are
>        finally written.

Noted, many times already. That's why I wrote "should be" - but in this
special scenario (filesystem speed tests) I don't care for file
integrity: if I pull the plug after "sync" and some data didn't make it
to the disks, I'll only look if the testscript got all the timestamps
and move on to the next test. I'm not testing for "filesystem integrity
after someone pulls the plug" here. And remember, I'm doing "sync" for
all the filesystems tested, so the comparison still stands.

Christian.

<Prev in Thread] Current Thread [Next in Thread>