public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>, linux-kernel@vger.kernel.org
Subject: Re: Abysmal disk performance, how to debug?
Date: Sat, 20 Jan 2007 21:19:23 +0100	[thread overview]
Message-ID: <20070120201923.GC25307@1wt.eu> (raw)
In-Reply-To: <200701202216.16637.ismail@pardus.org.tr>

On Sat, Jan 20, 2007 at 10:16:15PM +0200, Ismail Dönmez wrote:
> 20 Oca 2007 Cts 22:10 tarihinde, Tim Schmielau ??unlar?? yazm????t??: 
> [...]
> >
> > Note that these dd "benchmarks" are completely bogus, because the data=20
> > doesn't actually get written to disk in that time. For some enlightening=20
> > data, try
> >
> >   time dd if=3D/dev/zero of=3D/tmp/1GB bs=3D1M count=3D1024; time sync
> >
> > The dd returns as soon as all data could be buffered in RAM. Only sync=20
> > will show how long it takes to actually write out the data to disk.
> > also explains why you see better results is writeout starts earlier.
> 
> Still not that bad:
> 
> [~]> time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024;sync
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1,1 GB) copied, 53,3194 s, 20,1 MB/s
> 
> real    0m53.517s
> user    0m0.003s
> sys     0m3.193s

No, your measure is wrong because time measures "dd" and sync is done
after. Either use Tim's method (time sync) or the one I proposed in
previous mail (time dd | sync). Anyway, in your situation with a very
small buffer, this should not change by more than half a second or so.

Willy


  reply	other threads:[~2007-01-20 20:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 17:20 Abysmal disk performance, how to debug? Ismail Dönmez
2007-01-20 17:45 ` Willy Tarreau
2007-01-20 17:52   ` Ismail Dönmez
2007-01-20 18:03     ` Willy Tarreau
2007-01-20 18:06       ` Ismail Dönmez
2007-01-20 19:44       ` Sunil Naidu
2007-01-20 19:56         ` Stephen Clark
2007-01-20 20:09           ` Willy Tarreau
2007-01-21  3:41             ` Stephen Clark
2007-01-21  4:06               ` Gene Heskett
2007-01-27 19:43             ` Bill Davidsen
2007-02-03 17:22               ` Elladan
2007-01-20 20:05         ` Willy Tarreau
2007-01-20 20:11           ` Ismail Dönmez
2007-01-20 20:10     ` Tim Schmielau
2007-01-20 20:16       ` Ismail Dönmez
2007-01-20 20:19         ` Willy Tarreau [this message]
2007-01-20 20:28           ` Tim Schmielau
2007-01-20 20:31             ` Willy Tarreau
2007-01-20 20:21         ` Tim Schmielau
2007-01-20 20:28       ` Willy Tarreau
2007-01-20 20:39         ` Tim Schmielau
2007-01-20 21:24           ` Willy Tarreau
2007-01-20 21:41             ` Tim Schmielau
2007-01-20 21:12       ` Sunil Naidu
2007-01-20 22:00         ` Tim Schmielau
2007-01-20 23:47           ` Sunil Naidu

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=20070120201923.GC25307@1wt.eu \
    --to=w@1wt.eu \
    --cc=ismail@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    /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