> but that load of 21 is really just an artifact of a bunch
> of procs being in short-term io wait (D state in top/ps), right?
> such procs get counted in loadaverage, even though they're asleep,
> not eating cycles.
Well I tried running this:
while true; do uptime; ps -wax | grep -v ' S' | grep -v 'ps -wax'; sleep 5;
done
Which should show all procs not in the sleep state (except the ps process
itself) every 5 seconds, along with an uptime load. See output below, which
again has a load jump about half way down. It appears no extra processes are
in the 'D' state. And no extra CPU load appears either during the spike.
7:45pm up 1 day, 18:06, 2 users, load average: 0.29, 0.67, 2.11
7:45pm up 1 day, 18:07, 2 users, load average: 0.27, 0.66, 2.10
19784 ? R 0:00 /usr/local/apache/bin/httpd
7:45pm up 1 day, 18:07, 2 users, load average: 0.24, 0.65, 2.09
19808 ? R 0:00 /usr/local/apache/bin/httpd
7:45pm up 1 day, 18:07, 2 users, load average: 0.22, 0.64, 2.08
7:45pm up 1 day, 18:07, 2 users, load average: 0.21, 0.63, 2.07
7:45pm up 1 day, 18:07, 2 users, load average: 27.65, 6.46, 3.95
7:45pm up 1 day, 18:07, 2 users, load average: 25.44, 6.35, 3.93
7:45pm up 1 day, 18:07, 2 users, load average: 23.40, 6.25, 3.90
19668 ? R 0:00 imapd
19669 ? R 0:00 imapd
19742 ? D 0:00 imapd
7:45pm up 1 day, 18:07, 2 users, load average: 21.53, 6.14, 3.88
19784 ? R 0:01 /usr/local/apache/bin/httpd
7:45pm up 1 day, 18:07, 2 users, load average: 19.80, 6.04, 3.86
7:45pm up 1 day, 18:07, 2 users, load average: 18.22, 5.94, 3.84
I did notice a very small load jump earlier caused by what you describe
above, which seems to be due to the journal being flushed, but notice how
small this jump is in comparison to the one above...
7:38pm up 1 day, 18:00, 2 users, load average: 0.63, 1.47, 2.97
7:39pm up 1 day, 18:00, 2 users, load average: 0.58, 1.45, 2.96
18564 ? D 0:00 imapd
7:39pm up 1 day, 18:00, 2 users, load average: 0.53, 1.42, 2.94
7:39pm up 1 day, 18:01, 2 users, load average: 0.49, 1.40, 2.93
7:39pm up 1 day, 18:01, 2 users, load average: 0.53, 1.39, 2.92
7:39pm up 1 day, 18:01, 2 users, load average: 0.76, 1.41, 2.91
1441 ? D 1:23 qmgr -l -t fifo -u
7:39pm up 1 day, 18:01, 2 users, load average: 1.26, 1.50, 2.93
10 ? DW 17:08 [kjournald]
1577 ? D 0:00 imapd
16346 ? D 0:00 lmtpd -a
16393 ? D 0:00 imapd
16427 ? D 0:00 lmtpd -a
17349 ? D 0:00 imapd
17481 ? D 0:00 lmtpd -a
18356 ? D 0:00 imapd
7:39pm up 1 day, 18:01, 2 users, load average: 1.16, 1.48, 2.91
465 ? R 5:57 syslogd -m 0
7:39pm up 1 day, 18:01, 2 users, load average: 1.07, 1.45, 2.89
7:39pm up 1 day, 18:01, 2 users, load average: 0.98, 1.43, 2.88
7:39pm up 1 day, 18:01, 2 users, load average: 0.98, 1.42, 2.87
7:39pm up 1 day, 18:01, 2 users, load average: 0.90, 1.40, 2.85
7:40pm up 1 day, 18:01, 2 users, load average: 0.99, 1.41, 2.85
1
Now I'm more confused than ever, because there don't actually appear to be
any blocked processes at all? What is going on???
Rob Mueller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:45 EST