06-04-2016
The load is actually the number of "overdue" threads.
Most obvious is the run queue, threads that are waiting for a free CPU.
But there are threads waiting for something else, e.g. for an I/O driver or another blocked thread. If in user land they show up with state D, but there are also kernel threads that can "pile up" and add to the load.
This User Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. HP-UX
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
2. UNIX for Dummies Questions & Answers
Any reason why the "sum of all" average cpu utilization numbers collected from ps during any given time sample are "consistently" lower than the corresponding numbers reported by sar (%usr, %sys). We have a Solaris O/S 2.8.
We have been trying to correlate the CPU numbers from the sar, to the... (0 Replies)
Discussion started by: sevpert
0 Replies
3. Solaris
Hello,
i am using Solaris 10, The sar running in my system might be corrupted, but not sure why as there has been no updates to it ( to the best of my knowledge) and it was working fine until few days back. If i try to get sar reports using sar -o <filename> 60 180
there is no error but the... (2 Replies)
Discussion started by: nimi20
2 Replies
4. Shell Programming and Scripting
Deal All,
I'm writing a simple awk to generate some sort of report. The awk will check 24 files (file generated each one hour in a wholoe day) and then it will print one field to another file for counting purposes.
The script is working fine but the problem is that the CPU load is very high... (10 Replies)
Discussion started by: charbel
10 Replies
5. Shell Programming and Scripting
I receive on a daily basis CPU measures on a UNIX Server (AIX 5.3 version, korn shell). These CPU measures are provided by Omnivision tool.
We could see that Omnivision daily stats are not always equal to NMON stats regarding CPU level.
On my side (I work in an IT Production Support Team, not... (0 Replies)
Discussion started by: Scofield38
0 Replies
6. SuSE
Hi,
I had installed sysstat package below on a SUSE 11.4 box. I can see the sysstat cron file listed under the directory /etc/sysstat. However, it looks like the sysstat sar monitor is never run at all and the daily sar files are not created under the directory /var/log/sa. The cron daemon is also... (1 Reply)
Discussion started by: devtakh
1 Replies
7. AIX
Based on the documentation (Help - AIX 6.1 Information Center), I should be able to get the CPU utilization on a WPAR. But when I ran sar on the LPAR, I don't see the -@ option:
Usage: sar { -A | }
]] ]]
| ALL]
]
]
I'm on AIX 6.1. ... (0 Replies)
Discussion started by: PPPP
0 Replies
8. Shell Programming and Scripting
HI ,
I am wrirting a script for checking the performance monitoring on Linux System when my application is running.
I have to run a test for 30 minutes on some server and while the test is running i have to capture the perfromance metrics of Linux through vmstat , sar, mpstat, free.
here is the... (3 Replies)
Discussion started by: Anamica
3 Replies
9. UNIX for Dummies Questions & Answers
Hi, I'm John_giova and I'm new in this Forum. Sorry my english, it's not my first language.
So, I'm trying to check the CPU utlization during the video encoding and decoding (making a comparison between SW and HW ) using the SAR tool. According to a past thread I saw as CPU utilization I should... (4 Replies)
Discussion started by: John_giova
4 Replies
10. Solaris
need to capture the following data on an hourly basis without cronjob scheduling in Solaris 5.10/5.11:-
1. load averages
2. Total no. of processes.
3. CPU state
4. Memory
5. Top 3 process details.
any other third-party tool is available? (7 Replies)
Discussion started by: thoranam
7 Replies
UPTIME(1) User Commands UPTIME(1)
NAME
uptime - Tell how long the system has been running.
SYNOPSIS
uptime [options]
DESCRIPTION
uptime gives a one line display of the following information. The current time, how long the system has been running, how many users are
currently logged on, and the system load averages for the past 1, 5, and 15 minutes.
This is the same information contained in the header line displayed by w(1).
System load averages is the average number of processes that are either in a runnable or uninterruptable state. A process in a runnable
state is either using the CPU or waiting to use the CPU. A process in uninterruptable state is waiting for some I/O access, eg waiting for
disk. The averages are taken over the three time intervals. Load averages are not normalized for the number of CPUs in a system, so a
load average of 1 means a single CPU system is loaded all the time while on a 4 CPU system it means it was idle 75% of the time.
OPTIONS
-p, --pretty
show uptime in pretty format
-h, --help
display this help text
-s, --since
system up since, in yyyy-mm-dd HH:MM:SS format
-V, --version
display version information and exit
FILES
/var/run/utmp
information about who is currently logged on
/proc process information
AUTHORS
uptime was written by Larry Greenfield <greenfie@gauss.rutgers.edu> and Michael K. Johnson <johnsonm@sunsite.unc.edu>
SEE ALSO
ps(1), top(1), utmp(5), w(1)
REPORTING BUGS
Please send bug reports to <procps@freelists.org>
procps-ng December 2012 UPTIME(1)