Sponsored Content
Full Discussion: Load Average and Lwps
Operating Systems Solaris Load Average and Lwps Post 302415622 by jlliagre on Friday 23rd of April 2010 03:37:33 AM
Old 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

load average

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

Load Average

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

Determening load average.

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

top - Load average

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

load average query.

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

Please Help me in my load average

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

Load Average threshold

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

Load average in UNIX

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

Help with load average?

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

Load average unit

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
prstat(1M)																prstat(1M)

NAME
prstat - report active process statistics SYNOPSIS
prstat [-acJLmRtTv] [-C psrsetlist] [-j projlist] [-k tasklist] [-n ntop[,nbottom]] [-p pidlist] [-P cpulist] [-s key | -S key ] [-u euidlist] [-U uidlist] [-z zoneidlist] [-Z] [interval [count]] The prstat utility iteratively examines all active processes on the system and reports statistics based on the selected output mode and sort order. prstat provides options to examine only processes matching specified PIDs, UIDs, zone IDs, CPU IDs, and processor set IDs. The -j, -k, -C, -p, -P, -u, -U, and -z options accept lists as arguments. Items in a list can be either separated by commas or enclosed in quotes and separated by commas or spaces. If you do not specify an option, prstat examines all processes and reports statistics sorted by CPU usage. The following options are supported: -a Report information about processes and users. In this mode prstat displays separate reports about processes and users at the same time. -c Print new reports below previous reports instead of overprinting them. -C psrsetlist Report only processes or lwps that are bound to processor sets in the given list. Each processor set is identified by an integer as reported by psrset(1M). The load averages displayed are the sum of the load averages of the specified processor sets (see pset_getload- avg(3C)). Processes with one or more LWPs bound to processor sets in the given list are reported even when the -L option is not used. -j projlist Report only processes or lwps whose project ID is in the given list. Each project ID can be specified as either a project name or a numerical project ID. See project(4). -J Report information about processes and projects. In this mode prstat displays separate reports about processes and projects at the same time. -k tasklist Report only processes or lwps whose task ID is in tasklist. -L Report statistics for each light-weight process (LWP). By default, prstat reports only the number of LWPs for each process. -m Report microstate process accounting information. In addition to all fields listed in -v mode, this mode also includes the percentage of time the process has spent processing system traps, text page faults, data page faults, waiting for user locks and waiting for CPU (latency time). -n ntop[,nbottom] Restrict number of output lines. The ntop argument determines how many lines of process or lwp statistics are reported, and the nbottom argument determines how many lines of user, task, or projects statistics are reported if the -a, -t, -T, or -J options are specified. By default, prstat displays as many lines of output that fit in a window or terminal. When you specify the -c option or direct the out- put to a file, the default values for ntop and nbottom are 15 and 5. -p pidlist Report only processes whose process ID is in the given list. -P cpulist Report only processes or lwps which have most recently executed on a CPU in the given list. Each CPU is identified by an integer as reported by psrinfo(1M). -R Put prstat in the real time scheduling class. When this option is used, prstat is given priority over time-sharing and interactive pro- cesses. This option is available only for superuser. -s key Sort output lines (that is, processes, lwps, or users) by key in descending order. Only one key can be used as an argument. There are five possible key values: cpu Sort by process CPU usage. This is the default. pri Sort by process priority. rss Sort by resident set size. size Sort by size of process image. time Sort by process execution time. -S key Sort output lines by key in ascending order. Possible key values are the same as for the -s option. See -s. -t Report total usage summary for each user. The summary includes the total number of processes or LWPs owned by the user, total size of process images, total resident set size, total cpu time, and percentages of recent cpu time and system memory. -T Report information about processes and tasks. In this mode prstat displays separate reports about processes and tasks at the same time. -u euidlist Report only processes whose effective user ID is in the given list. Each user ID may be specified as either a login name or a numerical user ID. -U uidlist Report only processes whose real user ID is in the given list. Each user ID may be specified as either a login name or a numerical user ID. -v Report verbose process usage. This output format includes the percentage of time the process has spent in user mode, in system mode, and sleeping. It also includes the number of voluntary and involuntary context switches, system calls and the number of signals received. Statistics that are not reported are marked with the - sign. -z zoneidlist Report only processes or LWPs whose zone ID is in the given list. Each zone ID can be specified as either a zone name or a numerical zone ID. See zones(5). -Z Report information about processes and zones. In this mode, prstat displays separate reports about processes and zones at the same time. OUTPUT
The following list defines the column headings and the meanings of a prstat report: PID The process ID of the process. USERNAME The real user (login) name or real user ID. SIZE The total virtual memory size of the process, including all mapped files and devices, in kilobytes (K), megabytes (M), or gigabytes (G). RSS The resident set size of the process (RSS), in kilobytes (K), megabytes (M), or gigabytes (G). The RSS value is an estimate provided by proc(4) that might underestimate the actual resident set size. Users who want to get more accurate usage information for capacity plan- ning should use the -x option to pmap(1) instead. STATE The state of the process: cpuN Process is running on CPU N. sleep Sleeping: process is waiting for an event to complete. run Runnable: process in on run queue. zombie Zombie state: process terminated and parent not waiting. stop Process is stopped. PRI The priority of the process. Larger numbers mean higher priority. NICE Nice value used in priority computation. Only processes in certain scheduling classes have a nice value. TIME The cumulative execution time for the process. CPU The percentage of recent CPU time used by the process. If executing in a non-global zone and the pools facility is active, the percent- age will be that of the processors in the processor set in use by the pool to which the zone is bound. PROCESS The name of the process (name of executed file). LWPID The lwp ID of the lwp being reported. NLWP The number of lwps in the process. With the some options, in addition to a number of the column headings shown above, there are: NPROC Number of processes in a specified collection. MEMORY Percentage of memory used by a specified collection of processes. The following columns are displayed when the -v or -m option is specified USR The percentage of time the process has spent in user mode. SYS The percentage of time the process has spent in system mode. TRP The percentage of time the process has spent in processing system traps. TFL The percentage of time the process has spent processing text page faults. DFL The percentage of time the process has spent processing data page faults. LCK The percentage of time the process has spent waiting for user locks. SLP The percentage of time the process has spent sleeping. LAT The percentage of time the process has spent waiting for CPU. VCX The number of voluntary context switches. ICX The number of involuntary context switches. SCL The number of system calls. SIG The number of signals received. Under the -L option, one line is printed for each lwp in the process and some reporting fields show the values for the lwp, not the process. OPERANDS
The following operands are supported: count Specifies the number of times that the statistics are repeated. By default, prstat reports statistics until a termination signal is received. interval Specifies the sampling interval in seconds; the default interval is 5 seconds. Example 1: Reporting the Five Most Active Super-User Processes The following command reports the five most active super-user processes running on CPU1 and CPU2: example% prstat -u root -n 5 -P 1,2 1 1 PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/LWP 306 root 3024K 1448K sleep 58 0 0:00.00 0.3% sendmail/1 102 root 1600K 592K sleep 59 0 0:00.00 0.1% in.rdisc/1 250 root 1000K 552K sleep 58 0 0:00.00 0.0% utmpd/1 288 root 1720K 1032K sleep 58 0 0:00.00 0.0% sac/1 1 root 744K 168K sleep 58 0 0:00.00 0.0% init/1 TOTAL: 25, load averages: 0.05, 0.08, 0.12 Example 2: Displaying Verbose Process Usage Information The following command displays verbose process usage information about processes with lowest resident set sizes owned by users root and john. example% prstat -S rss -n 5 -vc -u root,john PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWP 1 root 0.0 0.0 - - - - 100 - 0 0 0 0 init/1 102 root 0.0 0.0 - - - - 100 - 0 0 3 0 in.rdisc/1 250 root 0.0 0.0 - - - - 100 - 0 0 0 0 utmpd/1 1185 john 0.0 0.0 - - - - 100 - 0 0 0 0 csh/1 240 root 0.0 0.0 - - - - 100 - 0 0 0 0 powerd/4 TOTAL: 71, load averages: 0.02, 0.04, 0.08 The following exit values are returned: 0 Successful completion. 1 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ proc(1), psrinfo(1M), psrset(1M), sar(1M), pset_getloadavg(3C), proc(4), project(4), attributes(5), zones(5) The snapshot of system usage displayed by prstat is true only for a split-second, and it may not be accurate by the time it is displayed. When the -m option is specified, prstat tries to turn on microstate accounting for each process; the original state is restored when prstat exits. See proc(4) for additional information about the microstate accounting facility. The total memory size reported in the SIZE and RSS columns for groups of processes can sometimes overestimate the actual amount of memory used by processes with shared memory segments. 13 Sep 2005 prstat(1M)
All times are GMT -4. The time now is 01:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy