From: "Sunil Naidu" <akula2.shark@gmail.com>
To: "Tim Schmielau" <tim@physik3.uni-rostock.de>
Cc: "Ismail Dönmez" <ismail@pardus.org.tr>,
"Willy Tarreau" <w@1wt.eu>,
linux-kernel@vger.kernel.org
Subject: Re: Abysmal disk performance, how to debug?
Date: Sun, 21 Jan 2007 02:42:42 +0530 [thread overview]
Message-ID: <8355959a0701201312r9a3aac4ufd151ca18ef7e64e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701202105210.23674@gockel.physik3.uni-rostock.de>
On 1/21/07, Tim Schmielau <tim@physik3.uni-rostock.de> wrote:
>
> Note that these dd "benchmarks" are completely bogus, because the data
> doesn't actually get written to disk in that time. For some enlightening
> data, try
>
> time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024; time sync
>
> The dd returns as soon as all data could be buffered in RAM. Only sync
> 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.
I am still getting better I feel:
[sukhoi@Typhoon ~]$ time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024; time sync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 19.5007 seconds, 55.1 MB/s
real 0m20.439s
user 0m0.004s
sys 0m4.535s
real 0m4.625s
user 0m0.000s
sys 0m0.125s
[sukhoi@Typhoon ~]$ 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, 20.8707 seconds, 51.4 MB/s
real 0m22.449s
user 0m0.002s
sys 0m4.922s
Linux used here is not 2.6.20-rc5, but it's a FC6 2.6.19 binary. Shall
post the results with 2.6.20-rc5.
BTW, does the results vary with a customized kernel (configured w.r.t
Processor & Hardware) than a generic kernel like FC6?
Are there any other such test cases?
>
> Tim
>
Thanks,
~Akula2
next prev parent reply other threads:[~2007-01-20 21:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 17:20 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
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 [this message]
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=8355959a0701201312r9a3aac4ufd151ca18ef7e64e@mail.gmail.com \
--to=akula2.shark@gmail.com \
--cc=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®