04-23-2010
Quote:
Originally Posted by
snjksh
1) Can any one tell me why the load average is so high though the cpu utilization is 85%.
Because there are some short periods of time where the run queue is empty and all threads are waiting for something to happen while there are more other periods of time when plenty of threads want a CPU but none is available. To know if this is an issue, you should tell how many CPUs/Cores/Chip Threads are available on your machine.
Quote:
2) what is lwps and is it harmfull for the system
lwps are light weight processes a.k.a threads. The number of lwps isn't harmful at all.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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)
Discussion started by: gfhgfnhhn
0 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: Heathe_Kyle
3 Replies
3. Shell Programming and Scripting
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)
Discussion started by: jibsonline
4 Replies
4. UNIX for Dummies Questions & Answers
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)
Discussion started by: govindts
8 Replies
5. Solaris
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)
Discussion started by: upengan78
5 Replies
6. UNIX for Dummies Questions & Answers
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)
Discussion started by: black-code
3 Replies
7. UNIX for Dummies Questions & Answers
What should be the threshold for load average of a quad core processor? What constitutes "good" and "bad" load average values? (2 Replies)
Discussion started by: proactiveaditya
2 Replies
8. UNIX for Advanced & Expert Users
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)
Discussion started by: kumaran_5555
2 Replies
9. UNIX for Dummies Questions & Answers
how load average is calculated and what exactly is it
difference between cpu% and load average (9 Replies)
Discussion started by: robo
9 Replies
10. HP-UX
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 NETBSD
rump_lwproc
RUMP_LWPROC(3) BSD Library Functions Manual RUMP_LWPROC(3)
NAME
rump_lwproc -- rump process/lwp management
LIBRARY
rump kernel (librump, -lrump)
SYNOPSIS
#include <rump/rump.h>
int
rump_pub_lwproc_rfork(int flags);
int
rump_pub_lwproc_newlwp(pid_t pid);
void
rump_pub_lwproc_switch(struct lwp *l);
void
rump_pub_lwproc_releaselwp();
struct lwp *
rump_pub_lwproc_curlwp();
DESCRIPTION
In a normal operating system model a process is a resource container and a thread (lwp) is the execution context. Every lwp is associated
with exactly one process, and a process is associated with one or more lwps. The current lwp (curlwp) indicates the current process and
determines which resources, such as UID/GID, current working directory, and file descriptor table, are currently used. These basic princi-
ples apply to rump kernels as well, but since rump uses the host's thread and process context directly, the rules for how thread context is
determined are different.
In the rump model, each host thread (pthread) is either bound to a rump kernel lwp or accesses the rump kernel with an implicit thread con-
text associated with pid 1. An implicit thread context is created every time the rump kernel is entered and disbanded upon exit. While con-
venient for occasional calls, creating an implicit thread uses a shared resource which can become highly contended in a multithreaded situa-
tion. It is therefore recommended that dedicated threads are created.
The association between host threads and the rump kernel curlwp is left to the caller. It is possible to create a dedicated host thread for
every rump kernel lwp or multiplex them on top of a single host thread. After rump lwps have been created, switching curlwp is very cheap --
faster than a thread context switch on the host. In case multiple lwps/processes are created, it is the caller's responsibility to keep
track of them and release them when they are no longer necessary. Like other rump kernel resources, procs/lwps will be released when the
process hosting the rump kernel exits.
rump_pub_lwproc_rfork()
Create a process, one lwp inside it and set curlwp to the new lwp. The flags parameter controls how file descriptors are inherited
from the parent. By default (flags=0) file descriptors are shared. Other options are:
RUMP_RFFDG Copy file descriptors from parent. This is what fork(2) does.
RUMP_RFCFDG File descriptors neither copied nor shared, i.e. new process does not have access to the parent's file descriptors.
This routine returns 0 for success or an errno indicating the reason for failure. The new process id can be retrieved in the normal
fashion by calling rump_sys_getpid().
rump_pub_lwproc_newlwp(pid)
Create a new lwp attached to the process specified by pid. Sets curlwp to the new lwp. This routine returns 0 for success or an errno
indicating the reason for failure.
rump_pub_lwproc_switch(l)
Sets curlwp to l. In case the new thread is associated with a different process than the current one, the process context is also
switched. The special value NULL sets curlwp to implicit context. Switching to an already running lwp, i.e. attempting to use the
same curlwp in two host threads simultaneously causes a fatal error.
rump_pub_lwproc_releaselwp()
Release curlwp and set curlwp to context. In case curlwp was the last thread inside the current process, the process container is also
released. Calling this routine without a dedicated curlwp is a fatal error.
rump_pub_lwproc_curlwp()
Returns curlwp or NULL if the current context is an implicit context.
SEE ALSO
getpid(2), rump(3)
HISTORY
rump_lwproc first appeared in NetBSD 6.0.
BSD
January 2, 2011 BSD