On 07/24/2009 04:41 PM, Aaron Konstam wrote:
Two suggestions:
1. run vmstat 2 30
to see how many context switches are occurring and the wait time for
processes etc. A load time of 11 means there are a large number of
processes waiting for cpu time. I think it is inaccurate to say no cpu
resources are being used.
Output here:
# vmstat 2 30
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
r b swpd free buff cache si so bi bo in cs us sy id wa st
3 0 444 173168 78832 911216 0 0 32 103 122 55 96 4 0 0 0
1 0 444 173168 78840 911216 0 0 0 326 1427 446 98 3 0 0 0
1 0 444 173168 78840 911216 0 0 0 0 1370 219 99 2 0 0 0
1 0 444 173044 78860 911216 0 0 0 162 1362 242 98 2 0 0 0
1 0 444 173044 78860 911216 0 0 0 0 1374 449 98 2 0 0 0
1 0 444 173044 78860 911216 0 0 0 0 1372 214 99 1 0 0 0
1 0 444 173044 78876 911216 0 0 0 156 1377 448 98 2 0 0 0
1 0 444 173044 78876 911216 0 0 0 0 1367 234 99 2 0 0 0
1 0 444 175648 78888 911216 0 0 0 38 1383 239 98 2 0 0 0
1 0 444 175648 78888 911216 0 0 0 0 1366 424 98 2 0 0 0
1 0 444 175648 78888 911216 0 0 0 0 1373 222 99 1 0 0 0
1 0 444 175648 78904 911216 0 0 0 80 1383 346 98 2 0 0 0
1 0 444 175648 78904 911216 0 0 0 0 1366 212 100 1 0 0 0
1 0 444 174656 78912 911208 0 0 0 30 1371 228 98 2 0 0 0
1 0 444 174656 78912 911216 0 0 0 0 1371 450 98 3 0 0 0
1 0 444 174656 78912 911216 0 0 0 0 1367 210 100 1 0 0 0
1 0 444 174656 78924 911216 0 0 0 34 1374 451 98 2 0 0 0
1 0 444 174656 78924 911216 0 0 0 0 1365 221 99 1 0 0 0
2 0 444 173184 78932 911216 0 0 0 204 1427 556 97 4 0 0 0
1 0 444 172548 78932 911224 0 0 0 0 1386 635 96 4 0 0 0
1 0 444 173168 78940 911224 0 0 0 150 1356 221 97 2 0 1 0
1 0 444 173168 78964 911224 0 0 0 34 1370 314 99 2 0 0 0
1 0 444 173168 78976 911224 0 0 0 1324 1375 228 99 1 0 0 0
1 0 444 172400 78984 911216 0 0 0 14 1377 246 98 2 0 0 0
1 0 444 172424 78984 911224 0 0 0 0 1364 433 99 1 0 0 0
1 0 444 172424 78984 911224 0 0 0 0 1371 220 99 1 0 0 0
1 0 444 172424 78992 911224 0 0 0 30 1375 461 98 3 0 0 0
1 0 444 172424 78992 911224 0 0 0 0 1365 207 100 1 0 0 0
1 0 444 172512 79000 911216 0 0 0 34 1377 237 98 2 0 0 0
1 0 444 172548 79000 911224 0 0 0 0 1376 451 97 3 0 0 0
Do you see anything in the above output? Load ave was 11.45 when I
started....
2. If you can get a hold of the article on the Real Time Scheduler found
in the August 2009 issue of Linux Journal. To me astropulse is running
away with your CPU time and noting else can get cpu adequate cpu time.
But its only July 2009! B^)
I'm no longer an LJ subscriber, so I'll have to either find/buy the
issue, or wait a while for it to become available on their WWW site.
Thanks Aaron!
--
Kevin J. Cummings
kjchome@xxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232 (http://counter.li.org)
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
