From: Andrew Morton <akpm@osdl.org>
To: Ravi Wijayaratne <ravi_wija@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Page Cache performance
Date: Fri, 16 Jan 2004 15:56:45 -0800 [thread overview]
Message-ID: <20040116155645.732e1fda.akpm@osdl.org> (raw)
In-Reply-To: <20040116191102.98783.qmail@web40602.mail.yahoo.com>
Ravi Wijayaratne <ravi_wija@yahoo.com> wrote:
>
> Hi All.
>
> We are running dbench on a machine with Dual Xeon (Hyper threading
> turned off), 1GB RAM
> and 4 Drive software RAID5. The kernel is 2.4.29-xfs 1.2. We are using
> LVM. However
> similar test done using ext2 on a disk partiotion (no md or LVM) shows
>
> The throughput is find till the number of clients are Around 16. At
> that point the throughput
> plummets about 40%. We are trying to avoid that and see how we could
> have a consistent throughput
> perhaps sacrificing some peak performance.
Once the amount of dirty memory in the machine hits 40% of the total, the
VM starts to initiate writeout. At 60% dirty the VM starts to deliberately
throttle the processes which are dirtying memory.
So you would expect to see extremely sudden transitions in overall
throughput at that point. Note that if the test were to run for a longer
period of time, or if it were to leave the files behind rather than
suddenly removing them you would not notice this effect.
The probability that dbench's access patterns have any similarity to the
access patterns of the application which you care about is vanishingly
small. The same can most probably be said of all the other off-the-shelf
benchmarks. They're not very impressive.
You will need to analyse your application's access patterns and design a
benchmark which reasonably closely and repeatably models them. Or, if
possible, use the live application itself.
prev parent reply other threads:[~2004-01-16 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:11 Ravi Wijayaratne
2004-01-16 20:34 ` Mike Fedyk
2004-01-16 23:56 ` Andrew Morton [this message]
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=20040116155645.732e1fda.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi_wija@yahoo.com \
/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®