Quote:
Originally Posted by
ucbus
please let me know if there is a command to do this.
Yes, there is. ;-))
Seriously,
vmstat provides all the information about runqueues you ever wanted to know. There are several threads dealing with an explanation about this command here, search for "vmstat" and "performance tuning". For instance,
this thread might interest you.
The first two columns of "vmstat", marked "r" and "b" are the "run queue" and "blocked queue". Typically the runqueue should be any number greater than zero and the blocked queue should be zero all the times. Rare occurrences of LOW(!) non-zero values (say a "1" every 5 pages of output) are tolerable, but should alert you already - the system is maybe at its max.
Regular non-zero values are a no-go and call for immediate (tuning-) action. Typically the system is memory-bound and therefore swapping. While the swapping takes place the process is blocked, hence the entry in the blocked-queue.
To find out about a running process use
ps. Usually it is difficult to track and pin a certain process in the runqueue, though, because the ever-changing content of this queue. You might want to look at
topas, this may give you the information you want.
I hope this helps.
bakunin
