From: Willy Tarreau <w@1wt.eu>
To: Sunil Naidu <akula2.shark@gmail.com>
Cc: "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:05:15 +0100 [thread overview]
Message-ID: <20070120200515.GA25307@1wt.eu> (raw)
In-Reply-To: <8355959a0701201144x290362d8ja6cd5bc1408475da@mail.gmail.com>
On Sun, Jan 21, 2007 at 01:14:41AM +0530, 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?
I don't suggest anything, this is already very good. The only goal of
reducing memory write cache is to get a more responsive system when
dumping massive amounts of data to disks, like above, because when
the system starts flushing the caches, you can only wait for it to
finish. But those tests are not realistic loads. A desktop and most
servers will benefit from large caches. But *some* workloads will
benefit from smaller caches if they consist in writing continuous
streams (eg: tcpdump or video recorders). What I suggested to the
user above was a way to get the system more responsive during his
test. It should not have changed the throughput at all if the
hardware was not a bit strange (well, it's a VAIO after all, I've
had one too, fortunately it died one month after the warranty,
putting an end to all my problems...).
Regards,
Willy
next prev parent reply other threads:[~2007-01-20 20:05 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 [this message]
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=20070120200515.GA25307@1wt.eu \
--to=w@1wt.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox