From: Willy Tarreau <w@1wt.eu>
To: Stephen Clark <Stephen.Clark@seclark.us>
Cc: "Sunil Naidu" <akula2.shark@gmail.com>,
"Ismail Dönmez" <ismail@pardus.org.tr>,
linux-kernel@vger.kernel.org
Subject: Re: Abysmal disk performance, how to debug?
Date: Sat, 20 Jan 2007 21:09:17 +0100 [thread overview]
Message-ID: <20070120200916.GB25307@1wt.eu> (raw)
In-Reply-To: <45B273E4.8040302@seclark.us>
On Sat, Jan 20, 2007 at 02:56:20PM -0500, Stephen Clark wrote:
> Sunil Naidu wrote:
>
> >On 1/20/07, Willy Tarreau <w@1wt.eu> wrote:
> >
> >
> >>It is not expected to increase write performance, but it should help
> >>you do something else during that time, or also give more responsiveness
> >>to Ctrl-C. It is possible that you have fast and slow RAM, or that your
> >>video card uses shared memory which slows down some parts of memory
> >>which are not used anymore with those parameters.
> >>
> >>
> >
> >I did test some SATA drives, am getting these value for 2.6.20-rc5:-
> >
> >[sukhoi@Typhoon ~]$ time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024
> >1024+0 records in
> >1024+0 records out
> >1073741824 bytes (1.1 GB) copied, 21.0962 seconds, 50.9 MB/s
> >
> >What can you suggest here w.r.t my RAM & disk?
> >
> >
> >
> >>Willy
> >>
> >>
> >
> >Thanks,
> >
> >~Akula2
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
> >
> >
> Hi,
> whitebook vbi s96f core 2 duo t5600 2gb hitachi ATA HTS721060G9AT00
> using libata
> time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 10.0092 seconds, 107 MB/s
>
> real 0m10.196s
> user 0m0.004s
> sys 0m3.440s
You have too much RAM, it's possible that writes did not complete before
the end of your measurement. Try this instead :
$ time dd if=/dev/zero of=/tmp/1GB bs=1M count=1024 | sync
Willy
next prev parent reply other threads:[~2007-01-20 20:09 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 [this message]
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
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=20070120200916.GB25307@1wt.eu \
--to=w@1wt.eu \
--cc=Stephen.Clark@seclark.us \
--cc=akula2.shark@gmail.com \
--cc=ismail@pardus.org.tr \
--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.