All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Chris Snook <csnook@redhat.com>,
	Emmanuel Florac <eflorac@intellique.com>,
	linux-kernel@vger.kernel.org
Subject: Re: RAID-1 performance under 2.4 and 2.6
Date: Fri, 28 Mar 2008 08:04:38 -0400	[thread overview]
Message-ID: <47ECDED6.4050100@tmr.com> (raw)
In-Reply-To: <e2e108260803280044o1bf41e5q8fd0b00a772b54a4@mail.gmail.com>

Bart Van Assche wrote:
> On Thu, Mar 27, 2008 at 10:53 PM, Bill Davidsen <davidsen@tmr.com> wrote:
>   
>> Bart Van Assche wrote:
>>     
>>> On Tue, Mar 25, 2008 at 11:00 PM, Chris Snook <csnook@redhat.com> wrote:
>>>       
>>>>  It means you shouldn't use dd as a benchmark.
>>>>         
>>> If you want to benchmark write speed, you should add
>>> oflag=direct,dsync to the dd command line. For benchmarking read speed
>>> you should specify iflag=direct. Or, even better, you can use xdd with
>>> the flags -dio -processlock.
>>>       
>>  No, you want your benchmark to measure performance doing what the
>>  application does. Do unless you have an application which has been
>>  heavily Linux-ized you don't want to measure something unrelated to the
>>  application requirements.
>>     
>
> A basic fact I learned in science classes: if you measure something,
> know very well what you measure and make sure your measurement is
> repeatable. But it was some time ago I learned this. Maybe the whole
> world changed since I learned that ?
>   

Sounds like we're saying the same thing. For naive applications dd is 
probably a closer model without direct or fconv, while if you want to 
see what you could gain using additional features those are useful 
options. I believe Chris was talking about the max speed possible, which 
is a good thing to know but not similar to simple programming or shell 
scripts using sed, grep, etc.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-03-28 12:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 18:43 RAID-1 performance under 2.4 and 2.6 Emmanuel Florac
2008-03-25 22:00 ` Chris Snook
2008-03-25 22:09   ` Emmanuel Florac
2008-03-25 22:47   ` Bill Davidsen
2008-03-25 23:13     ` Chris Snook
2008-03-25 23:42       ` Bill Davidsen
2008-03-26  8:05         ` Emmanuel Florac
2008-03-26  8:25           ` "J.A. Magallón"
2008-03-27 21:49             ` Bill Davidsen
2008-03-26 16:51           ` Chris Snook
2008-03-26 16:39         ` Chris Snook
2008-07-16 14:52       ` Pádraig Brady
2008-07-16 18:18         ` Chris Snook
2008-03-26  7:15   ` Bart Van Assche
2008-03-26  7:56     ` Emmanuel Florac
2008-03-27 21:53     ` Bill Davidsen
2008-03-28  7:44       ` Bart Van Assche
2008-03-28 12:04         ` Bill Davidsen [this message]
2008-03-25 22:37 ` Bill Davidsen
2008-03-26  8:42 ` Bart Van Assche
2008-03-26 11:07   ` Emmanuel Florac
2008-03-26 11:15     ` Bart Van Assche
2008-03-26 12:36       ` Emmanuel Florac
2008-03-26 13:22         ` Bart Van Assche
2008-03-27 22:03         ` Bill Davidsen

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=47ECDED6.4050100@tmr.com \
    --to=davidsen@tmr.com \
    --cc=bart.vanassche@gmail.com \
    --cc=csnook@redhat.com \
    --cc=eflorac@intellique.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.