11-23-2007
Look at the cpu percentage and the run queue.
The percentage shows how much of the time the CPU is being utilised (so 100% means continually), and the queue shows how many other processes are waiting to get some CPU cycles.
A 100% utilisation with an empty run queue means the system is performing exactly at capacity.
In glance (HP's tool, also available for Solaris, kindof like "top" on steroids), you can also select a process to zoom in on; if it shows the process is waiting on PRI, then that process is CPU bound.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are trying to Monitor Unix via Window95/98 on an NT network. Is there anyone that could point us in the direction on software that runs in Windows on a Telnet connection that we could use to accomplish this? We have tried a program called Unix Watcher by Etasoft and can' get it to connect.
... (6 Replies)
Discussion started by: btrout
6 Replies
2. UNIX for Advanced & Expert Users
hi,
can any one tell me, is there is any way i can check the performance of my solaris 8 os on an Ent 3500. Other than top to check for the top most processes, how to make the calculations with vmstat, iostat, mpstat and nfsstat. Or is there any other tools that i can use?
cheers. (3 Replies)
Discussion started by: i2admin
3 Replies
3. AIX
Hi All
I am looking for a script that would collect statistics in a summarised format.
CPU, Memory,Swap, Wait queue, Run queue and disk activity.
Something that would allow me to profile the environment based on a 1 line output that I could run every 15 min.
Thx
Junaid (1 Reply)
Discussion started by: jhansrod
1 Replies
4. UNIX for Advanced & Expert Users
Hi all
The place I work for is about to to place there database server under heavy load for testing and would like the effect recorded as much as possible.
Can anyone point me in the right direction with respect to real time system monitoring. I am aware of of 'sar', vmstat etc and hope to... (2 Replies)
Discussion started by: silvaman
2 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I am trying to find a way to view current CPU and disk usage. I used to use nmon which worked fine but since an upgrade to our servers this is no longer available. I have tried to get it reinstalled to no avail!
Are there any other commands you can use within unix which will allow me... (4 Replies)
Discussion started by: johnwilliams
4 Replies
6. UNIX for Dummies Questions & Answers
Which performance counters you might to define as "The most important counters in checking unix performance" (3 Replies)
Discussion started by: gen4ik
3 Replies
7. Linux
This is my first post (yes I'm a newbie).... :D
I'm looking for a list of Linux and Unix commands for performance monitoring and a good sight or area on this site that would have man pages and or information on those commands.....
Thanks if anyone can take the time to post..... :cool: (14 Replies)
Discussion started by: harrisjl
14 Replies
8. Solaris
Hi all,
I am planning to give a presentation on performance measure. I have decided to focus on the commands which are used to know the performance of the server. I have a idea of prstat,vmstat,netstat, and iostat. Could anybody suggest me any other commands which are used for perforamance... (7 Replies)
Discussion started by: priky
7 Replies
9. AIX
As I am new to the Unix field, I would like to get the clarification regarding the Filesystem.
The scenario is.. The filesystem (/drbackup) is getting monitored and if it exceeds the threshold, we will receive an alert from it. The issue is that we receive an alert with the description of... (2 Replies)
Discussion started by: A.Srenivasan
2 Replies
10. Shell Programming and Scripting
Hi,
I have been working on writing an automated script that will run 24x7 to monitor the performance parameters like CPU,Memory,Disk I/O,Network,SWAP Space etc for all types of Unix servers ( HP-UX,AIX,SOLARIS,LINUX).
Problem is I am confused with the commands top,prstat,vmstat,free,sar etc.... (4 Replies)
Discussion started by: ssk250
4 Replies
LEARN ABOUT FREEBSD
remrunqueue
RUNQUEUE(9) BSD Kernel Developer's Manual RUNQUEUE(9)
NAME
choosethread, procrunnable, remrunqueue, setrunqueue -- manage the queue of runnable processes
SYNOPSIS
#include <sys/param.h>
#include <sys/proc.h>
extern struct rq itqueues[];
extern struct rq rtqueues[];
extern struct rq queues[];
extern struct rq idqueues[];
struct thread *
choosethread(void);
int
procrunnable(void);
void
remrunqueue(struct thread *td);
void
setrunqueue(struct thread *td);
DESCRIPTION
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time
sharing processes, and idqueues for idle priority processes. Each priority queue consists of an array of NQS queue header structures. Each
queue header identifies a list of runnable processes of equal priority. Each queue also has a single word that contains a bit mask identify-
ing non-empty queues to assist in selecting a process quickly. These are named itqueuebits, rtqueuebits, queuebits, and idqueuebits. The
run queues are protected by the sched_lock mutex.
procrunnable() returns zero if there are no runnable processes other than the idle process. If there is at least one runnable process other
than the idle process, it will return a non-zero value. Note that the sched_lock mutex does not need to be held when this function is
called. There is a small race window where one CPU may place a process on the run queue when there are currently no other runnable processes
while another CPU is calling this function. In that case the second CPU will simply travel through the idle loop one additional time before
noticing that there is a runnable process. This works because idle CPUs are not halted in SMP systems. If idle CPUs are halted in SMP sys-
tems, then this race condition might have more serious repercussions in the losing case, and procrunnable() may have to require that the
sched_lock mutex be acquired.
choosethread() returns the highest priority runnable thread. If there are no runnable threads, then the idle thread is returned. This func-
tion is called by cpu_switch() and cpu_throw() to determine which thread to switch to. choosethread() must be called with the sched_lock
mutex held.
setrunqueue() adds the thread td to the tail of the appropriate queue in the proper priority queue. The thread must be runnable, i.e. p_stat
must be set to SRUN. This function must be called with the sched_lock mutex held.
remrunqueue() removes thread td from its run queue. If td is not on a run queue, then the kernel will panic(9). This function must be
called with the sched_lock mutex held.
SEE ALSO
cpu_switch(9), scheduler(9), sleepqueue(9)
BSD
August 15, 2010 BSD