Operating System - HP-UX
1846738 Members
3621 Online
110256 Solutions
New Discussion

TOP o/p..and sleep procecsses..

 
YOGI_3
Frequent Advisor

TOP o/p..and sleep procecsses..

HI all..Please find the attached file ..
contaning top o/p.
My query is CPU is not utilising too much..still 90% processes are in sleep State only..
even root processes are also in sleep state...

Urgent replies please..
There is never a wrong time to do the right things
2 REPLIES 2
Borislav Perkov
Respected Contributor

Re: TOP o/p..and sleep procecsses..

Hi,
Nothing to worry about it is normal situation especially for oracle. Don't forget that top command takes the values every 5 seconds. The process aren't waiting becuse of memory or cpu.
Regards,
Borislav
morganelan
Trusted Contributor

Re: TOP o/p..and sleep procecsses..

Processes can be described as being in one of the following states:

* idle - Process has either just been forked; an idle process can be
scheduled to run.

* run - Process is on a run queue, available to execute in either
kernel or user mode.

* stopped - Executing process is stopped by a signal or parent
process.

* sleep - Process is not executing, while on a sleep queue (for
example, awaiting I/O to complete).

* zombie - Having exited, the process no longer exists, but leaves
behind for the parent process some record of its execution.

When a program starts up a process, the kernel allocates a structure
for it from the process table; the process is now in idle state,
waiting for system resources. Once it acquires the resource, the
process is linked onto a run queue and made runnable. When the
process acquires a time-slice, it runs, switching as necessary between
kernel mode and user mode. If a running process receives a SIGSTOP
signal (as with control-Z in vi) or is being traced, it enters a stop
state. On receiving a SIGCONT signal, the process returns to a run
queue (in-core, runnable). If a running process must wait for a
resource (such as a semaphore or completion of I/O), the process goes
on a sleep queue (sleep state) until getting the resource, at which
time the process wakes up and is put on a run queue (in-core,
runnable). A sleeping process might also be swapped out, in which
case, when it receives its resource (or wakeup signal) the process
might be made runnable, but remain swapped out. The process is
swapped in and is put on a run queue. Once a process ends, it exits
into a zombie state.
Kamal Mirdad