* More VM benchmarks
@ 2004-02-04 2:29 Nick Piggin
2004-02-04 4:56 ` Nick Piggin
0 siblings, 1 reply; 3+ messages in thread
From: Nick Piggin @ 2004-02-04 2:29 UTC (permalink / raw)
To: Andrew Morton, linux-mm, linux-kernel
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.
The systime benchmarks are just a bit of fun. They don't
mean too much because I didn't measure how much work kswapd
is doing...
Oh, the base kernel is 2.6.2-rc3-mm1 for -np3. I'll release
the patches shortly.
Best regards,
Nick
--
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: More VM benchmarks
2004-02-04 2:29 More VM benchmarks Nick Piggin
@ 2004-02-04 4:56 ` Nick Piggin
2004-02-04 8:42 ` Nick Piggin
0 siblings, 1 reply; 3+ messages in thread
From: Nick Piggin @ 2004-02-04 4:56 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-mm, linux-kernel
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: More VM benchmarks
2004-02-04 4:56 ` Nick Piggin
@ 2004-02-04 8:42 ` Nick Piggin
0 siblings, 0 replies; 3+ messages in thread
From: Nick Piggin @ 2004-02-04 8:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-mm, linux-kernel
Nick Piggin wrote:
>
>
> Nick Piggin wrote:
>
>> http://www.kerneltrap.org/~npiggin/vm/5/
>>
Sorry to keep replying to myself. I've done some runs
with my IO scheduler regression tests and these patches
don't make a significant difference one way or the other
although the results with the patches are generally a
bit better.
Tested OraSim pgbench nickbench tiobench and the read/ls
kernel tree during a streaming read/write. 256MB RAM
this time.
--
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-02-04 8:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-04 2:29 More VM benchmarks Nick Piggin
2004-02-04 4:56 ` Nick Piggin
2004-02-04 8:42 ` Nick Piggin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox