Sponsored Content
Operating Systems HP-UX vmstat displays cpu idle time at 100% Post 302222369 by tfrye on Wednesday 6th of August 2008 05:43:39 PM
Old 08-06-2008
Here is a vmstat output and following is sar output on the same server.

procs memory page faults cpu
r b w avm free re at pi po fr de sr in sy cs us sy id
1 0 0 438406 32431 0 0 0 0 0 0 0 0 3 1 0 0 100
1 0 0 440543 32386 2 1 0 0 0 0 0 1036 10111 4016 0 0 100
1 0 0 440543 32386 2 0 0 0 0 0 0 1035 9864 3981 0 0 100
1 0 0 440543 32386 1 0 0 0 0 0 0 1041 10358 3994 0 0 100
1 0 0 440543 32386 0 0 0 0 0 0 0 1037 10075 3973 0 0 100
1 0 0 440543 32386 0 0 0 0 0 0 0 1035 9846 3961 0 0 100
1 0 0 440543 32386 0 0 0 0 0 0 0 1039 9718 3958 0 0 100
1 0 0 440543 32386 0 0 0 0 0 0 0 1045 9575 3948 0 0 100

HP-UX egateliv B.11.11 U 9000/800 08/06/08

16:39:22 %usr %sys %wio %idle
16:39:23 1 4 0 95
16:39:24 0 4 1 95
16:39:25 0 4 1 95
16:39:26 2 3 3 92
16:39:27 1 2 1 96
16:39:28 0 3 1 96
16:39:29 0 2 1 97
16:39:30 31 9 11 48
16:39:31 32 8 26 34
16:39:32 25 8 8 59
16:39:33 36 9 17 38
16:39:34 1 4 0 95
16:39:35 0 5 2 93
16:39:36 23 5 3 69
16:39:37 44 9 7 40
16:39:38 10 8 6 76
16:39:39 0 3 0 97
16:39:40 14 6 24 56
16:39:41 31 10 30 29
16:39:42 29 6 7 58
16:39:43 0 6 1 93
16:39:44 0 3 0 97
16:39:45 0 2 0 98
16:39:46 1 5 2 92
16:39:47 1 3 1 95

Average 11 5 6 77
 

10 More Discussions You Might Find Interesting

1. Solaris

CPU idle

hi when should we consider that CPU is loaded? When it is 100% idle or 0%idle?? tx (4 Replies)
Discussion started by: melanie_pfefer
4 Replies

2. HP-UX

sar output gives 98% idle CPU

Dear All, Our HPUX 8 GB 8CPU database server is behaving abnormally for the last 4+ weeks. I have generated a sar output and it is here- 11:46:52 %usr %sys %wio %idle 11:46:53 1 1 6 92 11:46:54 0 1 0 99 11:46:55 0 1 0... (3 Replies)
Discussion started by: Ashrunil
3 Replies

3. UNIX for Dummies Questions & Answers

CPU 0% idle - how do I find what was running?

Hi, I checking yesterday's SAR logs for one of our servers and it was showing that utilisation was down to 0% for 10 minutes at 2am. We're unaware of any jobs running at this time so need to find out which process caused this spike. Is there anything built into SAR (or does anything else exist)... (11 Replies)
Discussion started by: dlam
11 Replies

4. UNIX for Advanced & Expert Users

vmstat's cpu stats on first line of output are always the same

Hello, I'm seeing this problem with vmstat, where the first line of output always has the same CPU statistics. For example: neked@nekedmachine:~$ date && vmstat Fri Jul 24 06:57:08 EDT 2009 procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------ r b swpd ... (0 Replies)
Discussion started by: neked
0 Replies

5. Shell Programming and Scripting

How to get the information about cpu idle from top command?

I am using Ubuntu 9.04. I want to write a shell script to get the information about cpu idle from top command at the real time when i call it, compare cpu idle with 20 (20%), if cpu idle > 20 exit 1, vice versa exit 0. Anybody can help me to resolve it ? Thanks alot. (7 Replies)
Discussion started by: huyquocnguyen
7 Replies

6. Solaris

top is showing 0% cpu Idle

What should we do if we show a 0% cpu idl on top? (5 Replies)
Discussion started by: Pouchie1
5 Replies

7. Solaris

Why CPU idle 0 process nohub lose

Hello Solaris 8 when CPU idle 0 . why nohub process lose ? Thank (1 Reply)
Discussion started by: ppmanja
1 Replies

8. UNIX for Advanced & Expert Users

idle% cpu and run queue

Hi Everybody, Can anybody explain how CPU idle% is about 50%, but runq-sz more than 1? sar from Solaris 10: 00:00:05 %usr %sys %wio %idle 17:00:08 27 12 0 61 17:20:05 40 15 0 45 17:40:05 27 12 0 61 18:00:05 23... (2 Replies)
Discussion started by: sant
2 Replies

9. Red Hat

Monotring cpu and VMstat in Redhat Linux

Hi , Please some one help me out . How to write a shell cript to monitor cpu usage vmstat and in Redhat linux . vmstat out put should be in percentage. Thanks in advance !!!! (1 Reply)
Discussion started by: saanvi
1 Replies

10. UNIX for Dummies Questions & Answers

Idle Process Exhausting CPU

I noticed when having some trouble with code I was testing that the CPU was becoming exhausted and I would have to reboot. After rebooting a couple times I decided to check for other problems before trying my code again. That's when I noticed that the CPU with the idle process was through the roof:... (5 Replies)
Discussion started by: Azrael
5 Replies
VMSTAT(8)						   Linux Administrator's Manual 						 VMSTAT(8)

NAME
vmstat - Report virtual memory statistics SYNOPSIS
vmstat [-a] [-n] [delay [ count]] vmstat [-f] [-s] [-m] vmstat [-S unit] vmstat [-d] vmstat [-D] vmstat [-p disk partition] vmstat [-V] DESCRIPTION
vmstat reports information about processes, memory, paging, block IO, traps, disks and cpu activity. The first report produced gives averages since the last reboot. Additional reports give information on a sampling period of length delay. The process and memory reports are instantaneous in either case. Options The -a switch displays active/inactive memory, given a 2.5.41 kernel or better. The -f switch displays the number of forks since boot. This includes the fork, vfork, and clone system calls, and is equivalent to the total number of tasks created. Each process is represented by one or more tasks, depending on thread usage. This display does not repeat. The -m displays slabinfo. The -n switch causes the header to be displayed only once rather than periodically. The -s switch displays a table of various event counters and memory statistics. This display does not repeat. delay is the delay between updates in seconds. If no delay is specified, only one report is printed with the average values since boot. count is the number of updates. If no count is specified and delay is defined, count defaults to infinity. The -d reports disk statistics (2.5.70 or above required) The -D reports some summary statistics about disk activity. The -p followed by some partition name for detailed statistics (2.5.70 or above required) The -S followed by k or K or m or M switches changes the units of ouput from bytes to outputs between 1000, 1024, 1000000, or 1048576 bytes. Note this does not change the swap (si/so) or block (bi/bo) fields. The -V switch results in displaying version information. FIELD DESCRIPTION FOR VM MODE
Procs r: The number of processes waiting for run time. b: The number of processes in uninterruptible sleep. Memory swpd: the amount of virtual memory used. free: the amount of idle memory. buff: the amount of memory used as buffers. cache: the amount of memory used as cache. inact: the amount of inactive memory. (-a option) active: the amount of active memory. (-a option) Swap si: Amount of memory swapped in from disk (/s). so: Amount of memory swapped to disk (/s). IO bi: Blocks received from a block device (blocks/s). bo: Blocks sent to a block device (blocks/s). System in: The number of interrupts per second, including the clock. cs: The number of context switches per second. CPU These are percentages of total CPU time. us: Time spent running non-kernel code. (user time, including nice time) sy: Time spent running kernel code. (system time) id: Time spent idle. Prior to Linux 2.5.41, this includes IO-wait time. wa: Time spent waiting for IO. Prior to Linux 2.5.41, included in idle. st: Time stolen from a virtual machine. Prior to Linux 2.6.11, unknown. FIELD DESCRIPTION FOR DISK MODE
Reads total: Total reads completed successfully merged: grouped reads (resulting in one I/O) sectors: Sectors read successfully ms: milliseconds spent reading Writes total: Total writes completed successfully merged: grouped writes (resulting in one I/O) sectors: Sectors written successfully ms: milliseconds spent writing IO cur: I/O in progress s: seconds spent for I/O FIELD DESCRIPTION FOR DISK PARTITION MODE
reads: Total number of reads issued to this partition read sectors: Total read sectors for partition writes : Total number of writes issued to this partition requested writes: Total number of write requests made for partition FIELD DESCRIPTION FOR SLAB MODE
cache: Cache name num: Number of currently active objects total: Total number of available objects size: Size of each object pages: Number of pages with at least one active object NOTES
vmstat does not require special permissions. These reports are intended to help identify system bottlenecks. Linux vmstat does not count itself as a running process. All linux blocks are currently 1024 bytes. Old kernels may report blocks as 512 bytes, 2048 bytes, or 4096 bytes. Since procps 3.1.9, vmstat lets you choose units (k, K, m, M) default is K (1024 bytes) in the default mode vmstat uses slabinfo 1.1 FIXME FILES
/proc/meminfo /proc/stat /proc/*/stat SEE ALSO
iostat(1), sar(1), mpstat(1), ps(1), top(1), free(1) BUGS
Does not tabulate the block io per device or count the number of system calls. AUTHORS
Written by Henry Ware <al172@yfn.ysu.edu>. Fabian Frederick <ffrederick@users.sourceforge.net> (diskstat, slab, partitions...) Throatwobbler Ginkgo Labs 2009 Jan 9 VMSTAT(8)
All times are GMT -4. The time now is 08:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy