From: Roger Luethi <rl@hellgate.ch>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: Re: Memory management in 2.6
Date: Tue, 20 Jan 2004 14:11:59 +0100 [thread overview]
Message-ID: <20040120131159.GA5572@k3.hellgate.ch> (raw)
In-Reply-To: <400CB730.4010201@cyberone.com.au>
On Tue, 20 Jan 2004 16:05:52 +1100, Nick Piggin wrote:
>
> Andrew Morton wrote:
>
> >Nick Piggin <piggin@cyberone.com.au> wrote:
> >
> >>loads should be runnable on about 64MB, preferably give decently
> >>repeatable results in under an hour.
> >
> >In under three minutes, IMO.
>
> That would be nice, but sometimes hard, with multiple processes
> and fairly heavy swapping load.
efax exhibits a much higher run time variance in 2.6 than in 2.4, and
that's only one process. The reason we can't say anything conclusive
after three minutes is not a lack of short benchmarks, but the fact
that most benchmarks need to be repeated a dozen times to get reliable
numbers.
> would be preferable to "do something for 2 minutes and measure how
> far we got", but kbuild doesn't lend itself particularly well to
> that.
What you can do for kbuild is to build only part of it. I used something
like:
rm arch/*/*/*.o arch/i386/boot/bzImage
time make -j24
Roger
--
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>
next prev parent reply other threads:[~2004-01-20 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 4:51 Memory management in 2.6 Nick Piggin
2004-01-20 4:58 ` Andrew Morton
2004-01-20 5:05 ` Nick Piggin
2004-01-20 13:11 ` Roger Luethi [this message]
2004-01-20 7:00 ` Nigel Cunningham
2004-01-20 7:19 ` Michael Frank
2004-01-20 7:37 ` Nick Piggin
[not found] <20040127162346.37b75f6c.cliffw@osdl.org>
[not found] ` <40185564.8020709@cyberone.com.au>
2004-01-29 0:54 ` Memory Management " Nick Piggin
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=20040120131159.GA5572@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=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 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.