GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- TOP o/p..and sleep procecsses..
Operating System - HP-UX
1846738
Members
3621
Online
110256
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2005 08:37 PM
08-18-2005 08:37 PM
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..
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2005 09:02 PM
08-18-2005 09:02 PM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2005 09:13 PM
08-18-2005 09:13 PM
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.
* 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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP