01-12-2017
Sorry for not replying earlier, starting a new project kept me busy the lst few days.
There are a few things that don't quite add up IMHO:
First, the initial vmstat-output says ~200GB memory, but the avm column only shows ~21 mio of pages, which is ~80GB. Where is the difference? Please post the output of lsattr -El mem0 to verify how much (real) memory you really have.
Second, you said you have 15 cores configured, but the vmstat output shows 16. I presume that was just a typo on your part, but please confirm.
Third, further posted outputs of ps suggest that you have different DB instances running (fininddb and finabrodb). How many database instances are running simultaneously?
Fourth, i don't understand why there are so many archiver processes shown in the ps-outputs. What exactly is/are the DB(s) doing (in terms of how many requests and of which size typically) and how many logs (of which size) are typically produced per time unit? Are there any dumps being taken, exports running or the like?
In light of further information i am of the same opinion as Scrutinizer: your are perhaps a victim of double caching. The high number of pending I/Os and fs I/O blocked with no pbuf are further indicative of this assumption. If (see above, this is why this information is important) you have only one DB instance and you have 80GB of RAM and nothing else running on the system increase the SGA to ~60-70GB and see how that works. If you have set FILESYSTEMIO_OPTIONS=SETALL as suggested by agent.kgb Oracle should open its DB files with concurrent I/O even if the filesystem is not mounted with the CIO option. Concurrent I/O bypasses the OS caching of FS operations but i presume you haven't activated that yet otherwise the picture of two different caching systems blocking each other should not be seen even if the SGA is too small (as it probably is right now).
Finally, a suggestion: when you use vmstat on concurrent systems use the "-w" option. This way you get a neat table as output and it is easier to assess the picture.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
9 More Discussions You Might Find Interesting
1. AIX
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)
Discussion started by: wilder.mellotto
2 Replies
2. News, Links, Events and Announcements
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)
Discussion started by: MarkSeger
0 Replies
3. Solaris
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)
Discussion started by: mahive
4 Replies
4. Solaris
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)
Discussion started by: vijaysachin
1 Replies
5. HP-UX
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)
Discussion started by: GreenShery
8 Replies
6. SCO
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)
Discussion started by: ccc
7 Replies
7. HP-UX
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)
Discussion started by: sundar63
1 Replies
8. Shell Programming and Scripting
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)
Discussion started by: vegasluxor
3 Replies
9. Solaris
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 CENTOS
vmstat
VMSTAT(8) System Administration VMSTAT(8)
NAME
vmstat - Report virtual memory statistics
SYNOPSIS
vmstat [options] [delay [count]]
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
delay The delay between updates in seconds. If no delay is specified, only one report is printed with the average values since boot.
count Number of updates. In absence of count, when delay is defined, default is infinite.
-a, --active
Display active and inactive memory, given a 2.5.41 kernel or better.
-f, --forks
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.
-m, --slabs
Displays slabinfo.
-n, --one-header
Display the header only once rather than periodically.
-s, --stats
Displays a table of various event counters and memory statistics. This display does not repeat.
-d, --disk
Report disk statistics (2.5.70 or above required).
-D, --disk-sum
Report some summary statistics about disk activity.
-p, --partition device
Detailed statistics about partition (2.5.70 or above required).
-S, --unit character
Switches outputs between 1000 (k), 1024 (K), 1000000 (m), or 1048576 (M) bytes. Note this does not change the swap (si/so) or block
(bi/bo) fields.
-t, --timestamp
Append timestamp to each line
-w, --wide
Wide output mode (useful for systems with higher amount of memory, where the default output mode suffers from unwanted column break-
age). The output is wider than 80 characters per line.
-V, --version
Display version information and exit.
-h, --help
Display help and exit.
FIELD DESCRIPTION FOR VM MODE
Procs
r: The number of runnable processes (running or 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 (excluding tmpfs memory for
kernels 2.6.32+)
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
FILES
/proc/meminfo
/proc/stat
/proc/*/stat
SEE ALSO
free(1), iostat(1), mpstat(1), ps(1), sar(1), top(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...)
REPORTING BUGS
Please send bug reports to <procps@freelists.org>
procps-ng September 2011 VMSTAT(8)