I am wondering how we should interpret the CONTEST benchmark results.
I tried CONTEST with process_load on 2.6.12-rc3 (single CPU, P4 2.8G,
1G RAM). The CPU usage of kernel compiling is 28.9%, the load consumes
70.1% and the ratio is 3.98. Based on what Con says, the result is
bad since the ratio is high. I did some tracing and found the
background load (contest) runs at a dynamic priority of 115-120, which
is often higher than the dynamic priority of the kernel compiling
processes. This explains why the process_load consumes so much CPU.
My question is why is the result bad at all? One could certainly
argue that contest processes shouldn't consume so much CPU time since
they are considered to be background jobs. But why is kernel compiling
considered foreground jobs? Why making kernel compiling faster is
better? Actually, I am wondering if CONTEST is an appropriate
benchmark to report system responsiveness at all?
Any comments?
BTW, what benchmark do you guys use to test system responsiveness?
Haoqiang
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
