When using local drives, the load figure can be very high due to programs
waiting for files/directories residing on local drives that have been disconnected.
This leads to bad load balancing. A server that has 15 in load may very well
have place for more new sessions than a server that has 3 in load.
We should investigate if there is a better way of finding out how much CPU is used.
If easy, solve to 1.5.
We should probably use CPU time instead (which you can read from /proc/stat).
This also allows us to take into account io to local drives and ignore network
Investigate, but perhaps not to 2.1.0 if hard.
Time est is just how long time we're willing to devote for this cycle.