From: safemode <safemode@speakeasy.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: graphical swap comparison of aa and rik vm
Date: Thu, 1 Nov 2001 01:41:31 -0500 [thread overview]
Message-ID: <20011101064134Z278125-17408+8714@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10111010056100.31484-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10111010056100.31484-100000@coffee.psychology.mcmaster.ca>
On Thursday 01 November 2001 01:23, 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. 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.
>
> > Neadless to say that while running the test on either box, the entire
> > computer became unresponsive multiple times for extended lengths of
> > times.
>
> yes, unfortunately this corrupts the value of the data, since the
> timecourses are not really comparable, and samples are only vaguely related
> to time...
If you miss anything you miss the plateu data that would be found when the
IO peaks. But i doubt much at all was really lost in this case.
> regards, mark hahn.
Actually i found that most if not all of the vmstat's that weren't being
displayed were displayed immediately after the "locks", ie. I got flooded
with vmstats upon the computer becoming responsive again.
Of course I should have been timing each run with a stopwatch, but that never
crossed my mind that the vmstat would be lost. In other words i thought of
it as analogous to having burst-lag on irc. Guess that's for tomorrow after
work.
next prev parent reply other threads:[~2001-11-01 6:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 3:18 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 [this message]
2001-11-01 6:59 ` safemode
2001-11-01 11:08 ` Helge Hafting
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=20011101064134Z278125-17408+8714@vger.kernel.org \
--to=safemode@speakeasy.net \
--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 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®