> Well, on a laptop memory and disk bandwith are rarely wasted - they cost
> battery life.
I've been playing around with different scenarios to see the differences
in performance. A good way to trigger the cache problem is to untar a
couple of kernel source trees or other large amounts of files, until free
memory is down to less than 2mb. Then try to fire up a few apps that need
some memory. The hard drive thrashes around as the VM tries to free up
enough space, often using swap instead of flushing out the cache.
These source trees can then be deleted which frees up the memory the cache
was using and performance returns to where it should be.
However, if I just fire up enough apps to use up all the memory and then
go into swap, response is still acceptable. If the app requires loading
from swap there is just a short lag while the VM does its thing and then
life is good.
I don't expect to be able to run more apps than I have memory for without
a performance hit, but I do expect to be able to run with over 128MB of
"real" free memory and not suffer from performance degradation (which
doesn't happen at present)
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
