@tmpsantos,thanks for your new solution idea! :-)

I have read the article carefully, and here is my opinion:
There are 3 solutions to evaluate the performance of a Linux system or cluster given by this atricle.
1. "instant load": the number of tasks in the system task queue at the very instant.
2. "load averages" (you prefer this?): the average number of active tasks in the last 1, 5 or 15 minutes.
3. "CPU usage ratio":the percentage represents that how much time each CPU of the system spent processing in a short time interval (usually one second).

Personally, I prefer the current solution 3# more than solution 2#, and the reasons are below:
1. solution 1# and 2# actually evaluate "system load" not "CPU load". I don't think they are fully same. When talking about "system load", Maybe we should consider about "memory usage ratio" "cache state" even "scheduling algorithm", not only about "CPU load". so solution 3# is more match the spec definition.
2. The number of active tasks given by solution 1# and 2# is not user-friendly and developer-frendly. Maybe Users and developers will not care about the tasks' status, but the view of CPU usage ratio.

Is it OK to you? If I am wrong, please correct me, Thanks!