Load averages are just that - load data gathered over a period of time, then averaged
ex.: disk busy % from iostat command, gathered once an hour
"load" can be defined as cpu utilization or disk utilization or memory utilization. Or all three. The primary concern about when load becomes an issue is when proccesses are forced to wait for the cpu, wait execessivly for I/O, wait for processes to swap in/out of memory.
thankyou jim
so how to judge what value of load average is good for a system considering approximate value for system resources
we have an unix system which has
load average normally about 20.
but while i am running a particular unix batch which performs heavy
operations on filesystem and database average load
reduces to 15.
how can we explain this situation?
while running that batch idle cpu time is about %60-65... (0 Replies)
Hello all, I have a question about load averages.
I've read the man pages for the uptime and w command for two or three different flavors of Unix (Red Hat, Tru64, Solaris). All of them agree that in the output of the 2 aforementioned commands, you are given the load average for the box, but... (3 Replies)
Hi,
I'm new to shell scripting. I need to make a script to add on to my cronjobs.
The script must get the value of load average from my server and if its greater than 10 it should stop my apache service. I cant find a way to get the value of load average in integer type to do the check. Any... (4 Replies)
Hello, Here is the output of top command. My understanding here is,
the load average 0.03 in last 1 min, 0.02 is in last 5 min, 0.00 is in last 15 min.
By seeing this load average, When can we say that, the system load averge is too high?
When can we say that, load average is medium/low??... (8 Replies)
Hi,
i have installed solaris 10 on t-5120 sparc enterprise.
I am little surprised to see load average of 2 or around on this OS.
when checked with ps command following process is using highest CPU. looks like it is running for long time and does not want to stop, but I do not know... (5 Replies)
Hello AlL,..
I want from experts to help me as my load average is increased and i dont know where is the problem !!
this is my top result :
root@a4s # top
top - 11:30:38 up 40 min, 1 user, load average: 3.06, 2.49, 4.66
Mem: 8168788k total, 2889596k used, 5279192k free, 47792k... (3 Replies)
Hi ,
I am using 48 CPU sunOS server at my work.
The application has facility to check the current load average before starting a new process to control the load.
Right now it is configured as 48. So it does mean that each CPU can take maximum one proces and no processe is waiting.
... (2 Replies)
Hi,
On load average graph, unit is 100m, 200m, 300...800m.
I don't understand what it means.
Thx for helping (3 Replies)
Discussion started by: Michenux
3 Replies
LEARN ABOUT HPUX
ruptime
ruptime(1) General Commands Manual ruptime(1)NAME
ruptime - show status of local machines
SYNOPSIS DESCRIPTION
outputs a status line for each machine on the local network that is running the daemon. status lines are formed from packets broadcast
once every 3 minutes between daemons (see rwhod(1M)) on each host on the network. Each status line has a field for the name of the
machine, the status of the machine (up or down), how long the machine has been up or down, the number of users logged into the machine, and
the 1-, 5- and 15-minute load averages for the machine when the packet was sent.
The status of the machine is reported as ``up'' unless no report has been received from the machine for 11 minutes or more.
The length of time that the machine has been up is shown as:
Load averages are the average number of jobs in the run queue over the last 1-, 5- and 15-minute intervals when the packet was sent.
An example status line output by might be:
The above status line would be interpreted as follows:
is presently ``up'' and has been up for 1 day, 5 hours and 15 minutes. It currently has 7 users logged in. Over the last 1-minute inter-
val, an average of 1.47 jobs were in the run queue. Over the last 5-minute interval, an average of 1.16 jobs were in the run queue. Over
the last 15-minute interval, an average of 0.80 jobs were in the run queue.
If a user has not used the system for an hour or more, the user is considered idle. Idle users are not shown unless the option is speci-
fied.
Options
If no options are specified, the listing is sorted by host name. Options change sorting order as follows:
Sort by load average.
Sort by up time.
Sort by the number of users.
Reverse the sort order.
DIAGNOSTICS
No status report files in
Ask the system administrator to check whether the daemon is running.
AUTHOR
was developed by the University of California, Berkeley.
FILES
Data files
SEE ALSO rwho(1), rwhod(1M).
ruptime(1)