linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: John Stoffel <stoffel@casc.com>,
	Tobias Ringstrom <tori@unhappy.mine.nu>,
	Jonathan Morton <chromi@cyberspace.org>,
	Shane Nay <shane@minirl.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	"Dr S.M. Huen" <smh1008@cus.cam.ac.uk>,
	Sean Hunter <sean@dev.sportingbet.com>,
	Xavier Bestel <xavier.bestel@free.fr>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: VM Report was:Re: Break 2.4 VM in five easy steps
Date: 09 Jun 2001 14:31:49 +0200	[thread overview]
Message-ID: <87u21p3kcq.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.33.0106082013500.672-100000@mikeg.weiden.de> (Mike Galbraith's message of "Fri, 8 Jun 2001 20:30:32 +0200 (CEST)")

Mike Galbraith <mikeg@wen-online.de> writes:

> On Fri, 8 Jun 2001, John Stoffel wrote:
> 
> > Mike> OK, riddle me this.  If this test is a crummy test, just how is
> > Mike> it that I was able to warn Rik in advance that when 2.4.5 was
> > Mike> released, he should expect complaints?  How did I _know_ that?
> > Mike> The answer is that I fiddle with Rik's code a lot, and I test
> > Mike> with this test because it tells me a lot.  It may not tell you
> > Mike> anything, but it does me.
> >
> > I never said it was a crummy test, please do not read more into my
> > words than was written.  What I was trying to get across is that just
> > one test (such as a compile of the kernel) isn't perfect at showing
> > where the problems are with the VM sub-system.
> 
> Hmm...
> 
> Tobias> Could you please explain what is good about this test?  I
> Tobias> understand that it will stress the VM, but will it do so in a
> Tobias> realistic and relevant way?
> 
> I agree, this isn't really a good test case.  I'd rather see what
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> happens when you fire up a gimp session to edit an image which is
> *almost* the size of RAM, or even just 50% the size of ram.  Then how
> does that affect your other processes that are running at the same
> time?
> 
> ...but anyway, yes it just one test from any number of possibles.

One great test that I'm using regularly to see what's goin' on, is at
http://lxr.linux.no/. It is a cool utility to cross reference your
Linux kernel source tree, and in the mean time eat gobs of memory, do
lots of I/O, and burn many CPU cycles (all at the same time). Ideal
test, if you ask me and if anybody has the time, it would be nice to
see different timing numbers when run on different kernels. Just make
sure you run it on the same kernel tree to make reproducable results.
It has three passes, and the third one is the most interesting one
(use vmstat 1 to see why). When run with 64MB RAM configuration, it
would swap heavily, with 128MB somewhat, and at 192MB maybe not
(depending on the other applications running at the same time).

Try it, it is a nice utility, and a great test. :)
-- 
Zlatko
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-06-09 12:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0106071722450.1156-100000@freak.distro.conectiva>
2001-06-07 23:29 ` Shane Nay
2001-06-08  1:18   ` Jonathan Morton
2001-06-08 12:50     ` Mike Galbraith
2001-06-08 14:19       ` Tobias Ringstrom
2001-06-08 15:51         ` John Stoffel
2001-06-08 17:01           ` Mike Galbraith
2001-06-08 17:43             ` John Stoffel
2001-06-08 17:35               ` Marcelo Tosatti
2001-06-08 20:58                 ` John Stoffel
2001-06-08 20:04                   ` Marcelo Tosatti
2001-06-08 23:44                     ` Jonathan Morton
2001-06-09  2:36                       ` Andrew Morton
2001-06-09  3:43                       ` Mike Galbraith
2001-06-09  4:05                         ` Jonathan Morton
2001-06-09  5:09                           ` Mike Galbraith
2001-06-09  5:07                 ` Mike Galbraith
2001-06-08 18:30               ` Mike Galbraith
2001-06-09 12:31                 ` Zlatko Calusic [this message]
2001-06-09  3:34             ` Rik van Riel
2001-06-08 16:51         ` Mike Galbraith
2001-06-08 19:09           ` Tobias Ringstrom
2001-06-09  4:36             ` Mike Galbraith

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=87u21p3kcq.fsf@atlas.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=chromi@cyberspace.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mikeg@wen-online.de \
    --cc=sean@dev.sportingbet.com \
    --cc=shane@minirl.com \
    --cc=smh1008@cus.cam.ac.uk \
    --cc=stoffel@casc.com \
    --cc=tori@unhappy.mine.nu \
    --cc=xavier.bestel@free.fr \
    /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