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.
Jonathan Morton has been using another large compile to also test the
sub-system, and it includes a compile which puts a large, single
process pressure on the VM. I consider this to be a more
representative test of how the VM deals with pressure.
The kernel compile is an ok test of basic VM handling, but from what
I've been hearing on linux-kernel and linux-mm is that the VM goes to
crap when you have a mix of stuff running, and one (or more) processes
starts up or grows much larger and starts impacting the system
I'm also not knocking your contributions to this discussion, so stop
being so touchy. I was trying to contribute and say (albeit poorly)
that a *mix* of tests is needed to test the VM.
More importantly, a *repeatable* set of tests is what is needed to
test the VM and get consistent results from run to run, so you can see
how your changes are impacting performance. The kernel compile
doesn't really have any one process grow to a large fraction of
memory, so dropping in a compile which *does* is a good thing.
John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
email@example.com - http://www.lucent.com - 978-952-7548
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/