In my oracle db server we have 15 cores (power8). The output of the vmstat is as below.
Now you can see the run queue and wait queue both are high also entitled capacity is also always 90%. The 15 to 25% cpu is always idle. So is there a cpu bottleneck on this system or its ok, no one complaining but want to know for myself.
Last edited by Don Cragun; 12-29-2016 at 03:46 AM..
Reason: Add CODE tags.
Hello everybody.
I have a problem with my AIX 5.3. Recently my unix shows a high cpu utilization with sar or topas.
I need to find what I have to do to solve this problem, in fact, I don't know what is my problem.
I had the same problem with another AIX 5.3 running the same... (2 Replies)
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Hello Friends,
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
=========================================================================
$ prstat -a
... (4 Replies)
Hi All,
While creating zone we will mention min and max cpu cores, like
add dedicated-cpu
set ncpus=NUM_CPUS_MIN-NUM_CPUS_MAX
end
Ques1:
Suppose thing that non global zone uses only minimum cores at particular time What the other cores will do, Will it shared to global zone?
Ques:2... (1 Reply)
There might be some problem with my server,
because every morning at 7, it's performance become bad with no DB extra deadlock.
But I just couldn't figure it out.
Please give me some advise, thanks a lot...
According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%.
... (8 Replies)
hi
We have migrated SCO 5.0.6 into ESX4, but the VM eats 100% of the virtual CPU.
Here is top print from the SCO VM:
last pid: 16773; load averages: 1.68, 1.25, 0.98 02:08:41
79 processes: 75 sleeping, 2 running, 1 zombie, 1 onproc
CPU states: 0.0% idle, 17.0% user,... (7 Replies)
We have a DB server which is constantly utilised above 95% above.
This is becoming nuisance when the monitoring team frequently calls to check on it. Frankly I do not know what to tweak or even interpret the outputs.
I noticed constant 30 to 60% in wio column of the cpu utilisation.
There... (1 Reply)
I want to write a shell script which will print AIX
CPU utilization
memory utilization
every 5 mins redirect to file. How do i do it? Please advise.
Which commands I should use? (3 Replies)
Hi all,
Been reading a lot of the cpu load and its "analogy of it to car traffic path of expressway"
From wiki
Most UNIX systems count only processes in the running (on CPU) or runnable (waiting for CPU) states. However, Linux also includes processes in uninterruptible sleep states... (13 Replies)
Discussion started by: javanoob
13 Replies
LEARN ABOUT BSD
vmstat
VMSTAT(1) General Commands Manual VMSTAT(1)NAME
vmstat - report virtual memory statistics
SYNOPSIS
vmstat [ -fsi ] [ drives ] [ interval [ count ] ]
DESCRIPTION
Vmstat delves into the system and normally reports certain statistics kept about process, virtual memory, disk, trap and cpu activity. If
given a -f argument, it instead reports on the number of forks and vforks since system startup and the number of pages of virtual memory
involved in each kind of fork. If given a -s argument, it instead prints the contents of the sum structure, giving the total number of
several kinds of paging related events which have occurred since boot. If given a -i argument, it instead reports on the number of inter-
rupts taken by each device since system startup.
If none of these options are given, vmstat will report in the first line a summary of the virtual memory activity since the system has been
booted. If interval is specified, then successive lines are summaries over the last interval seconds. ``vmstat 5'' will print what the
system is doing every five seconds; this is a good choice of printing interval since this is how often some of the statistics are sampled
in the system; others vary every second, running the output for a while will make it apparent which are recomputed every second. If a
count is given, the statistics are repeated count times. The format fields are:
Procs: information about numbers of processes in various states.
r in run queue
b blocked for resources (i/o, paging, etc.)
w runnable or short sleeper (< 20 secs) but swapped
Memory: information about the usage of virtual and real memory. Virtual pages are considered active if they belong to processes which are
running or have run in the last 20 seconds. A ``page'' here is 1024 bytes.
avm active virtual pages
fre size of the free list
Page: information about page faults and paging activity. These are averaged each five seconds, and given in units per second.
re page reclaims (simulating reference bits)
at pages attached (found in free list)
pi pages paged in
po pages paged out
fr pages freed per second
de anticipated short term memory shortfall
sr pages scanned by clock algorithm, per-second
up/hp/rk/ra: Disk operations per second (this field is system dependent). Typically paging will be split across several of the available
drives. The number under each of these is the unit number.
Faults: trap/interrupt rate averages per second over last 5 seconds.
in (non clock) device interrupts per second
sy system calls per second
cs cpu context switch rate (switches/sec)
Cpu: breakdown of percentage usage of CPU time
us user time for normal and low priority processes
sy system time
id cpu idle
If more than 4 disk drives are configured in the system, vmstat displays only the first 4 drives, with priority given to Massbus disk
drives (i.e. if both Unibus and Massbus drives are present and the total number of drives exceeds 4, then some number of Unibus drives will
not be displayed in favor of the Massbus drives). To force vmstat to display specific drives, their names may be supplied on the command
line.
FILES
/dev/kmem, /vmunix
SEE ALSO systat(1), iostat(1)
The sections starting with ``Interpreting system activity'' in Installing and Operating 4.2bsd.
4th Berkeley Distribution March 15, 1986 VMSTAT(1)