Load average measures how many tasks are waiting; it does not measure how long they wait. Every alarm built on the three numbers in /proc/loadavg is therefore a queue-depth alarm pretending to be a latency alarm, and the gap between

Load average measures how many tasks are waiting; it does not measure how long they wait. Every alarm built on the three numbers in /proc/loadavg is therefore a queue-depth alarm pretending to be a latency alarm, and the gap between
"Connection timed out" is not one error — it is the single symptom of at least seven different failure states, and the timeout's own arithmetic tells you which one you have: on Linux, a TCP connect that receives no reply