From: Daniel Phillips <phillips@bonn-fries.net>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.8-pre1 and dbench -20% throughput
Date: Sat, 28 Jul 2001 00:34:05 +0200 [thread overview]
Message-ID: <0107280034050V.00285@starship> (raw)
In-Reply-To: <200107272112.f6RLC3d28206@maila.telia.com>
In-Reply-To: <200107272112.f6RLC3d28206@maila.telia.com>
On Friday 27 July 2001 23:08, Roger Larsson wrote:
> Hi all,
>
> I have done some throughput testing again.
> Streaming write, copy, read, diff are almost identical to earlier 2.4
> kernels. (Note: 2.4.0 was clearly better when reading from two files
> - i.e. diff - 15.4 MB/s v. around 11 MB/s with later kenels - can be
> a result of disk layout too...)
>
> But "dbench 32" (on my 256 MB box) results has are the most
> interesting:
>
> 2.4.0 gave 33 MB/s
> 2.4.8-pre1 gives 26.1 MB/s (-21%)
>
> Do we now throw away pages that would be reused?
>
> [I have also verified that mmap002 still works as expected]
Could you run that test again with /usr/bin/time (the GNU time
function) so we can see what kind of swapping it's doing?
The use-once approach depends on having a fairly stable inactive_dirty
+ inactive_clean queue size, to give use-often pages a fair chance to
be rescued. To see how the sizes of the queues are changing, use
Shift-ScrollLock on your text console.
To tell the truth, I don't have a deep understanding of how dbench
works. I should read the code now and see if I can learn more about it
:-/ I have noticed that it tends to be highly variable in performance,
sometimes showing variation of a few 10's of percents from run to run.
This variation seems to depend a lot on scheduling. Do you see "*"'s
evenly spaced throughout the tracing output, or do you see most of them
bunched up near the end?
--
Daniel
next prev parent reply other threads:[~2001-07-27 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 21:08 2.4.8-pre1 and dbench -20% throughput Roger Larsson
2001-07-27 21:42 ` Rik van Riel
2001-07-27 22:34 ` Daniel Phillips [this message]
2001-07-27 23:43 ` Roger Larsson
2001-07-28 1:11 ` Daniel Phillips
2001-07-28 0:35 ` Steven Cole
2001-07-28 2:04 ` Daniel Phillips
2001-07-30 13:15 ` Marcelo Tosatti
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=0107280034050V.00285@starship \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@skelleftea.mail.telia.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