From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: More VM benchmarks
Date: Wed, 04 Feb 2004 15:56:07 +1100 [thread overview]
Message-ID: <40207B67.7040407@cyberone.com.au> (raw)
In-Reply-To: <40205908.4080600@cyberone.com.au>
Nick Piggin wrote:
> http://www.kerneltrap.org/~npiggin/vm/5/
>
> OK I'm not too unhappy with kbuild now. I've flattened the
> curve a bit more since you last saw it. Would be nice if we
> could get j8 and j10 faster but you can't win them all.
>
> I'm not sure what happens further on - Roger indicates that
> perhaps 2.4 overtakes 2.6 again at j24 although the patchset
> he used (http://www.kerneltrap.org/~npiggin/vm/3/) performs
> far worse than this one at j16. This is really not a big
> deal IMO, but I might run it and see what happens.
>
They're about even here at an hour apiece. Thats good,
not that I would ever try to optimise for this case...
2.6.2-rc3-mm1-np3
kbuild: make -j24 bzImage
144.45user 31.58system 1:00:08elapsed 4%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (380524major+919600minor)pagefaults 0swaps
npiggin@ropeable:~/vm$ cat bkb-24.out
2.4.23
kbuild: make -j24 bzImage
148.41user 43.11system 1:02:41elapsed 5%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (612476major+633988minor)pagefaults 0swaps
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: More VM benchmarks
Date: Wed, 04 Feb 2004 15:56:07 +1100 [thread overview]
Message-ID: <40207B67.7040407@cyberone.com.au> (raw)
In-Reply-To: <40205908.4080600@cyberone.com.au>
Nick Piggin wrote:
> http://www.kerneltrap.org/~npiggin/vm/5/
>
> OK I'm not too unhappy with kbuild now. I've flattened the
> curve a bit more since you last saw it. Would be nice if we
> could get j8 and j10 faster but you can't win them all.
>
> I'm not sure what happens further on - Roger indicates that
> perhaps 2.4 overtakes 2.6 again at j24 although the patchset
> he used (http://www.kerneltrap.org/~npiggin/vm/3/) performs
> far worse than this one at j16. This is really not a big
> deal IMO, but I might run it and see what happens.
>
They're about even here at an hour apiece. Thats good,
not that I would ever try to optimise for this case...
2.6.2-rc3-mm1-np3
kbuild: make -j24 bzImage
144.45user 31.58system 1:00:08elapsed 4%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (380524major+919600minor)pagefaults 0swaps
npiggin@ropeable:~/vm$ cat bkb-24.out
2.4.23
kbuild: make -j24 bzImage
148.41user 43.11system 1:02:41elapsed 5%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (612476major+633988minor)pagefaults 0swaps
--
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-02-04 4:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 2:29 More VM benchmarks Nick Piggin
2004-02-04 2:29 ` Nick Piggin
2004-02-04 4:56 ` Nick Piggin [this message]
2004-02-04 4:56 ` Nick Piggin
2004-02-04 8:42 ` Nick Piggin
2004-02-04 8:42 ` 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=40207B67.7040407@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.