AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When doing some machine audits on an IBM rs6000 (aix 4.3.3.0 <--- lowest ML), i typed:
ps -aux and the following returned (it has been truncated for shortness here):
# ps aux|more
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 24.8 1.0 8 6352 - A Aug 04 239054:44 kproc
root 774 23.7 1.0 8 6352 - A Aug 04 227883:55 kproc
root 1032 23.1 1.0 8 6352 - A Aug 04 222423:01 kproc
root 1290 23.0 1.0 8 6352 - A Aug 04 221316:33 kproc
----- MORE HERE BUT DELETED -----
What are commands: kproc ? And why are the chewing up the cpu percentage?
This is a 4 cpu machine. While typing ' w ' the following returns:
# w
07:09PM up 167 days, 4:11, 8 users, load average: 1.68, 1.39, 1.47
however there are no jobs called kproc running on the machine (that is, jobs called kproc executed by regular users).
Worth mentioning that the CPU is always doing something. The idle process is the process it runs when nothing is happening so it does not show up most stats.
When the CPU becomes busy, idle goes down (of course).
Is the size of your idle process percentage a good indicator of how your hardware is handling the software? Also, is this cumulative or the current status? What I mean is does the idle process percentage calculate all of the idle time from the last reboot, or is this just the most recent five minutes?
Originally posted by jc2it Is the size of your idle process percentage a good indicator of how your hardware is handling the software? Also, is this cumulative or the current status? What I mean is does the idle process percentage calculate all of the idle time from the last reboot, or is this just the most recent five minutes?
Run vmstat (e.g. vmstat 2). Ignore the first line (which shows stats since the last reboot) and look at the others which show current system performance.
The last four columns are usr, sys, idle and wait. Usr + sys is the total time the CPU is spending doing things. As a rule of thumb, on a normal system with interactive users (i.e. not doing batch processing) you want this to be below 70%. If the CPU usr + sys is consistently high, that's an indication that the system has too little processing power.
The "wait" is the system waiting for I/O. Again a very rough rule of thumb, but on a normal interactive workload you want this to be below 30%. If wait i/o is high, you can use iostat (or topas, or a few other tools) to identify hot spots. Idle in itself isn't very useful - you need to know whether the non-idle time is doing CPU work or waiting for I/O.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.