Sponsored Content
Operating Systems Solaris Solaris 10 : Memory Capping Query Post 302249206 by trevagreene on Monday 20th of October 2008 09:56:43 PM
Old 10-20-2008
Solaris 10 : Memory Capping Query

Hi Folks,
Im running solaris 10 8/07 and im trying to set up some memory capping within zones for the system project.

ie.
zone1# cat /etc/project
system:0::::rcap.max-rss=41943040
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::

zone2# cat /etc/project
system:0::::rcap.max-rss=31457280
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::


Now this seems to to work fine as when I check this Im getting the results I expect to see.
ie

zone1# rcapstat
id project nproc vm rss cap at avgat pg avgpg
0 system 30 192M 84M 40M 37G 0K 11G 0K

zone2# rcapstat
id project nproc vm rss cap at avgat pg avgpg
0 system 30 240M 31M 30M 42G 0K 11G 0K



However, when I check the memory usage of these zones from the global zone I get different results..

root@au11qap1i0tels2 [112] > prstat -n16 -Z


ZONEID NPROC SWAP RSS MEMORY TIME CPU ZONE
5 33 193M 84M 0.5% 0:05:43 0.3% zone1
6 33 240M 71M 0.4% 0:05:43 0.3% zone2
0 68 783M 798M 4.9% 19:05:07 0.0% global



Can someone let me know if this is a quirk with the way the rcapd communicates with the global zone ? or is something not right here ?

Thanx in advance.
 

10 More Discussions You Might Find Interesting

1. Solaris

Memory usage in Solaris - memory not freed?

Hi, I'm running a multi-process software system on a Solaris 8 machine. When I monitor the memory usage, I see that the free memory is dropping rapidly, but I can't detect a process that uses this memory. I'm using "top" to get the free memory and the memory usage of processes. Thanks. (3 Replies)
Discussion started by: gewurtz
3 Replies

2. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

3. Solaris

Solaris 10 - capping CPU

Hi all I've purchased a T3-1 server. The T3-1 has a 16 core CPU. I want to create a zone to install an Oracle DB server in. Due to Oracle licensing issues I want to limit the zone to 8 cores. I've done some research and it seems there are 2 ways of setting a CPU core limit for a zone. 1. ... (0 Replies)
Discussion started by: soliberus
0 Replies

4. Red Hat

Query on RAM Memory

Hi Experts, I have a linux system , which triggers a alarm if RAM memory goes above 70%... When i see top command i cant find any process utilizing much of memory .. Can anyone tell me what could be the reason for high memory utilization.. Bellow is the free command o/p: free ... (14 Replies)
Discussion started by: shaliniyadav
14 Replies

5. Solaris

Resource Capping Help!

Hi guys. Quick question for some hopefully ;-) When using resource capping (for CPU in this case). If a container is restricted to use a single CPU/core, are the other containers intelligent enough to know that they have fewer CPU's available to them? My question relates to a T2000 which... (7 Replies)
Discussion started by: boneyard
7 Replies

6. Programming

Memory Allocation Query

When we dynamically allocate the memory say 100 integers say int *x = new int(1000); then does entire chunk of memory gets allocated at once after the completion of the statement? I mean will the the concept of page fault come into picture over here? (3 Replies)
Discussion started by: rupeshkp728
3 Replies

7. UNIX for Advanced & Expert Users

Query regarding swap memory

Hi, Please help explain and answer the below: 1. I need to predetermine how much swap will my JVM use if it is started with -Xms 512M and -Xmx 1024M ? 2. Can a JVM process just use the Heap and not the Swap memory ? 3. If the Total physical RAM on my server is 8 GB and current Heap... (6 Replies)
Discussion started by: mohtashims
6 Replies

8. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

Hi Experts, Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing. Why memory utilization on solaris always looks high? I have statement about memory on solaris, is this true: Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies

9. Solaris

Need to understand CPU capping in Zones

Hi All I am using below command to do zone capping #zonecfg -z zone1 zonecfg:zone1> zonecfg:zone1>add capped-cpu zonecfg:zone1>capped-cpu> set ncpus=2 zonecfg:zone1>capped-cpu> end zonecfg:zone1> commit zonecfg:zone1> exit It means that it can used two CPUs in zone1 then I run... (5 Replies)
Discussion started by: sb200
5 Replies

10. Solaris

Memory capping Solaris 11.3

I want to allocate RAM : 64GB (Dedicated allocation) Swap : 8GB Please assist and recommend the correct capping values capped-memory: physical: XXG Had allocated physical=64GB, Swap=8GB, and locaked 16GB and found my non-global zone were unable to use... (1 Reply)
Discussion started by: Shirishlnx
1 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 07:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy