@tmpsantos we were using `getloadavg(3)` when develop the Tizen SystemInfo. Your simple agrithm were ever thought, while that is not so accurate for multi-core situation. 

Suppose an app is very CPU sensitive, for instance encrypting data with mutil-thread(via worker), when the load of  `getCPUInfo()` return >= 0.9, then downgrade workers number to release more CPU cycles. 

If you use the simple logic as you said above, 120%(turn to 100%) on dual core system is not the same meaning of 100% on single core system. While that will cause my app goes with low CPU way.

If you think user can bear that vague situation, let's use the simple way. Personally, I prefer report the meaning data which is keeping current solution.

@hmin(the DC spec author)'s option should be more considered.