From: Helge Hafting <helgehaf@idb.hist.no>
To: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: graphical swap comparison of aa and rik vm
Date: Thu, 01 Nov 2001 12:08:54 +0100 [thread overview]
Message-ID: <3BE12D46.780477E@idb.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.10.10111010056100.31484-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>
> > Here is the graph http://safemode.homeip.net/vm_swapcomparison.png . It's
>
> here's my munge of the same data:
> http://mhahn.mcmaster.ca/~hahn/foo.png
> the measures I find interesting are the SI/SO rates. first, the most obvious
> feature is that Rik-VM has a serious problem knowing when to *stop* swapping
> out. but SO isn't a bad thing unless it's obsessive: it's when you see high
> *swap-in* that you know the VM has previously chosen bad pages to SO.
Sure. SO isn't bad for the benchmark, but think of the guy trying
to use the machine after the test finished. It probably swapped out
a lot of other processes which is why you didn't see it swap in again.
These things weren't needed for the bench, but daily use don't
look like that. If my big job takes a long time - no problem
if I can work on something else with nice performance.
> and this is the second big difference: Rik-VM doesn't make nearly as many
> mistakes - especially look at Andrea-VM thrashing out-in-out at ~ samples 26-32.
>
> also, if you merely sum the SI and SO columns for each:
> sum(SI) sum(SO) sum(SI+SO)
> Rik-VM 43564 317448 290032
> AA-VM 118284 171748 361012
> to me, this looks like the same point: Rik being SO-happy,
> Andrea having to SI a lot more. interesting also that Andrea wins the race,
> in spite of poorer SO choices and more swap traffic overall.
It'd be real interesting to know wether or not the "excessive" swapping
caused extra seeks. Readahead or simply reading more consecutive blocks
don't hurt - while seeks do. Perhaps this is why it didn't hurt so
much?
Also consider the multiuser aspect - punishing a memory pig with
extra swapin isn't necessarily so bad, if it keeps more memory around
for others. Could possibly be bad for a dedicated box, but Andrea won
on speed anyway.
Helge Hafting
next prev parent reply other threads:[~2001-11-01 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 3:18 graphical swap comparison of aa and rik vm safemode
2001-11-01 3:41 ` Alex Pennace
2001-11-01 3:50 ` safemode
2001-11-01 6:10 ` safemode
2001-11-01 6:23 ` Mark Hahn
2001-11-01 6:41 ` safemode
2001-11-01 6:59 ` safemode
2001-11-01 11:08 ` Helge Hafting [this message]
2001-11-01 12:10 ` Rik van Riel
2001-11-01 13:47 ` safemode
2001-11-02 4:18 ` safemode
2001-11-01 21:23 ` Dirk Moerenhout
[not found] <20011102041819.4C36238C0A@perninha.conectiva.com.br>
2001-11-02 11:17 ` Rik van Riel
2001-11-02 13:07 ` safemode
[not found] <20011102130750.1760138C77@perninha.conectiva.com.br>
2001-11-02 13:14 ` Rik van Riel
2001-11-02 23:48 ` safemode
2001-11-03 15:36 ` safemode
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=3BE12D46.780477E@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=hahn@physics.mcmaster.ca \
--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.