03-31-2010
I'll try to explain the percentages to the best of my knowledge:
- idle: should be obvious
- user: the time the processes run in user space. That is loops and all in-memory operations
- kernel: the time spent in kernel space. Everything I/O runs in kernel space, that is: reading & writing files, network communication, user I/O (when not sleeping), loading/forking new processes, ...
- iowait: the time waiting for an I/O device to come ready. As long as this is 0, none of your processes had to wait for a disk to come ready, or was blocked by a slow net connection.
- swap: if this is zero it basically means none of your processes had to be swapped out, so your current memory installation is enough.
10 More Discussions You Might Find Interesting
1. Solaris
Hi..,
my dout is a solaris server is having 16 cpu's.
in tht one cpu running some error process, accupaying more space.
I wanna down tht particular CPU only with out interrupting the other 15
CPU's. how can i do this. is there any command for this ?? (5 Replies)
Discussion started by: b.janardhanguru
5 Replies
2. UNIX for Dummies Questions & Answers
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 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
Can anyone tell me difference between cpu-shares vs cpu-cap in solaris & how FSS will work with cpu-caps ? (9 Replies)
Discussion started by: fugitive
9 Replies
5. Solaris
Hi,
I am a weblogic Admin
I our env there are 5 servers running in one Solaris 10 Sparc machine.
But when i tried for process status using <top> command
I got the following output
load averages: 1.75, 2.18, 2.12; up 134+08:28:49
22:24:21
79 processes: 77 sleeping, 1 running,... (1 Reply)
Discussion started by: Joseph Antoine
1 Replies
6. Solaris
Hi All,
What is the difference between CPU CHIP and CUP ID on SUN/ Oracle M5000 servers..
Thanks in advance (3 Replies)
Discussion started by: kumarmani
3 Replies
7. Solaris
I want to investigate why CPU utilization was high yesterday on my solaris 10 machine.
I have been reported this problem but how can I investigate why CPU utilization went high at that time? :confused: (4 Replies)
Discussion started by: kashif_islam
4 Replies
8. UNIX for Dummies Questions & Answers
We have a single threaded application which is restricted by CPU usage even though there are multiple CPUs on the server, hence leading to significant performance issues. Is it possible to merge / combine multiple CPUs at OS level so it appear as a single CPU for the application? (6 Replies)
Discussion started by: Dissa
6 Replies
9. AIX
Hi All,
It may be a n00b question, but i really want to know , How Entitled Capacity is less and Used CPU is more when there is no Free CPU is available in the managed system.
I have 5LPARs in a MS with Dual VIO.
Managed System CPU details
Available: 0.20
Assigned to partitions: 15.80... (11 Replies)
Discussion started by: Thala
11 Replies
10. UNIX for Beginners Questions & Answers
I read that Entitlement CPU should be set to max 75% compare to Virtual CPU. May I know the reason.
I have set the Entitlement CPU = Virtual CPU on AIX . It works fine .
Can you help to understand. (1 Reply)
Discussion started by: gabhanes
1 Replies
memx(8) System Manager's Manual memx(8)
Name
memx - memory exerciser
Syntax
/usr/field/memx [ -h ] [ -s ] [ -ofile ] [ -ti ] [ -mj ] [ -pk ]
Description
The memory exerciser spawns processes to exercise memory by writing and reading three patterns: 1's and 0's, 0's and 1's, and a random pat-
tern.
You specify the number of processes to spawn and the size of memory to be tested by each process. The first process is a shared memory
exerciser, the remaining are standard memory exercisers. The exerciser will run until the process receives a or a kill -15 pid.
A logfile is made in for you to examine and then remove. If there are errors in the logfile, check the file, where the driver and kernel
error messages are saved.
Options
The options are:
-h Print the help message for the command.
-s Disable shared memory testing.
-ofile Save diagnostic output in file.
-ti Run time in minutes (i). The default is to run until the process receives a or a kill -15 pid.
-mj The memory size in bytes (j) to be tested by each spawned process. Must be greater than 4095. The default is (total-memory)/20.
-pk The number of processes to spawn (k). The default is 20. The maximum is also 20.
Restrictions
The exerciser is restricted by the size of swap space available. The size of the swap space and the size of internal memory available will
determine how many processes can run on the system. For example, If there were 16Mbytes of swap space and 16Mbytes of memory, all of the
swap space would be used if all 20 spawned memory exercisers were running. In that event, no new processes would be able to run. On sys-
tems with large amounts of memory and small swap space, you must restrict the number of memory exercisers and/or the size of memory being
tested.
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
Examples
The following example tests all of memory by running 20 spawned processes until a or kill -15 pid is received.
% /usr/field/memx
The following example runs 10 spawned processes, memory size 500,000 bytes, for 180 minutes in the background.
% /usr/field/memx -t180 -m500000 -p10 &
See Also
Guide to System Exercisers
memx(8)