linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-mm@kvack.org
Subject: Re: VM benchmarks
Date: Sun, 1 Feb 2004 16:08:18 -0800	[thread overview]
Message-ID: <20040201160818.1499be18.akpm@osdl.org> (raw)
In-Reply-To: <401D8D64.8010605@cyberone.com.au>

Nick Piggin <piggin@cyberone.com.au> wrote:
>
> After playing with the active / inactive list balancing a bit,
> I found I can very consistently take 2-3 seconds off a non
> swapping kbuild, and the light swapping case is closer to 2.4.
> Heavy swapping case is better again. Lost a bit in the middle
> though.
> 
> http://www.kerneltrap.org/~npiggin/vm/4/
> 
> At the end of this I might come up with something that is very
> suited to kbuild and no good at anything else. Do you have any
> other ideas of what I should test?
> 

The thing people most seem to complain about is big compilations.

Things like a bitkeeper consistency check while dinking with the X UI have
also been noted, but that's a bit hard to quantify.

Maybe ask Roger to try his efax workload?


--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-02-02  0:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 23:36 Nick Piggin
2004-02-02  0:08 ` Andrew Morton [this message]
2004-02-02  0:11   ` Nick Piggin
2004-02-02  6:31     ` Martin J. Bligh
2004-02-02  7:51       ` Nick Piggin
2004-02-02 16:50     ` Roger Luethi
2004-02-02 23:17       ` Nick Piggin
2004-02-03 23:16         ` Roger Luethi
2004-02-04  0:13           ` Nick Piggin
2004-02-04 15:27 ` Koni
2004-02-04 15:57   ` Martin J. Bligh

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=20040201160818.1499be18.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=piggin@cyberone.com.au \
    /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