On 11/21/2010 9:05 AM, Per Jessen wrote:
Carlos E. R. wrote:
On Sunday, 2010-11-21 at 10:47 +0100, Per Jessen wrote:
It's not the CPU-load but lack of memory that'll stop it though.
Then, what it needs is an option that instead of launching a fixed number of threads, launchs a variable number of threads that doesn't cause swap to be used. Dynamically checking overall system load.
If anything else uses swap, it'll never start. Besides, it's not really a job for 'make' (and others who submit jobs in parallel, e.g. xargs).
Did you guys miss the point that he only used -j64 to try to load the system in a way that would normally result in terrible user interactive desktop perfromance, and test that the new cgroups hack causes the desktop and other user interactive processes to get cpu and i/o scheduling no matter how loaded the rest of the system is? A method that dynamically runs the correct optimal -jN is exactly what you don't want in a stress test. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org