Sponsored Content
Full Discussion: prstat RSS memory
Operating Systems Solaris prstat RSS memory Post 302466620 by k4boy on Tuesday 26th of October 2010 08:19:32 PM
Old 10-26-2010
SunOS 5.9 sun4u sparc and Oracle 10.2.0.4
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help with prstat

Hello, The last line of prstat shows load average. I am unable to figure out what actually it is. I have read the man pages and also googled, all for no use. Can somebody help me, as to what should be the avg. load of the system for best performance and how is this load of prstat calculated. (6 Replies)
Discussion started by: vibhor_agarwali
6 Replies

2. Post Here to Contact Site Administrators and Moderators

Rss

Could RSS-support mod be installed for this forum? (3 Replies)
Discussion started by: eugrus
3 Replies

3. Solaris

Top and Prstat display different results for memory

I have a question about the accuracy of prstat. I did a 'prstat -t' and it shows 99% of my memory is occupied by oracle. NPROC USERNAME SIZE RSS MEMORY TIME CPU 194 oracle 343G 340G 99% 86:17.24 56% However, 'top' shows I still have 7762meg of memory free. Memory: 16G real, 7762M... (4 Replies)
Discussion started by: zen03
4 Replies

4. Solaris

prstat

hi all, was trying to figure out how busy my app was by looking at the performance of the app server. did a 'prstat -s rss' command to find the app servers using most memory. Found a command 'prstat -m' which is meant to show more details on each pid but the output of this command... (1 Reply)
Discussion started by: cesarNZ
1 Replies

5. Solaris

100% memory usage in prstat

Hi Guys, I have observed the Oracle (DB USER) is utilizing 100% of the memory in the prstat -a output. I am bit confused is it normal and if not how to bring it down? ABout the machine it is a SunOS 5.10 Generic_125100-10 sun4v sparc SUNW,Sun-Fire-T200. Please see below output of prstat -a... (12 Replies)
Discussion started by: Asteroid
12 Replies

6. Solaris

Free memory in top and prstat command

Hi Export, i execute 'top' command to show the free memory in Solaris host, but the read is much lower than the RSS value shown in prstat command. Which one can reflect the real status and it is possible the difference caused by any patch of OS? Top command (only 883 memory is free)... (3 Replies)
Discussion started by: eiga
3 Replies

7. Solaris

RSS pmap and prstat

Hi, I have some question about memory in Solaris. How it's possible that prstat -a show me that some process using 230M RSS and when I'm using pmap -x show me that this same process using only 90M RSS ? (0 Replies)
Discussion started by: deivo
0 Replies

8. Solaris

Prstat rss and swap

Hi, someone please explain me what's the difference b/w rss and swap in PRSTAT. i'm getting output like below, NPROC USERNAME SWAP RSS MEMORY TIME CPU 70 weblogic 48G 46G 73% 449:17:03 0.4% swap always remains... (11 Replies)
Discussion started by: sunnys7143
11 Replies

9. Solaris

RSS of prstat vs RSS of PS

Hi, When I sum the RSS number in the ps command for a specific user and compare it with the RSS values of the prstat command of the same user - there is a big difference. Server details: Solaris 10 5/09 s10s_u7wos_08 SPARC prstat output: NPROC USERNAME SWAP RSS MEMORY TIME ... (2 Replies)
Discussion started by: amitlib
2 Replies
platform(4)							   File Formats 						       platform(4)

NAME
platform - directory of files specifying supported platforms SYNOPSIS
.platform DESCRIPTION
The Solaris operating environment release includes the .platform directory, a new directory on the Solaris CD image. This directory con- tains files (created by Sun and Solaris OEMs) that define platform support. These files are generically referred to as platform definition files. They provide a means to map different platform types into a platform group. Platform definition files in the .platform directory are used by the installation software to ensure that software appropriate for the architecture of the system will be installed. Sun provides a platform definition file named .platform/Solaris . This file is the only one that can define platform groups to which other platform definition files can refer. For example, an OEM platform definition file can refer to any platform group specified in the Solaris platform definition file. Other platform definition files are delivered by OEMs. To avoid name conflicts, OEMs will name their platform definition file with an OEM- unique string. OEMs should use whatever string they use to make their package names unique. This unique string is often the OEM's stock symbol. Comments are allowed in a platform definition file. A "#" begins a comment and can be placed anywhere on a line. Platform definition files are composed of keyword-value pairs, and there are two kinds of stanzas in the file: platform group definitions and platform identifications. o Platform group definitions: The keywords in a platform group definition stanza are: PLATFORM_GROUP The PLATFORM_GROUP keyword must be the first keyword in the platform group definition stanza. The value assigned to this keyword is the name of the platform group, for example: PLATFORM_GROUP=sun4c The PLATFORM_GROUP name is an arbitrary name assigned to a group of platforms. However, PLATFORM_GROUP typically equals the output of the uname -m command. PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of all platforms in the platform group, for example: INST_ARCH=sparc The INST_ARCH keyword value must be the value returned by the uname -p command on all platforms in the platform group. o Platform identifications: The keywords in a platform identification stanza are: PLATFORM_NAME The PLATFORM_NAME keyword must be the first keyword in the platform identification stanza. The PLATFORM_NAME is the name assigned to the platform, for example: PLATFORM_NAME=SUNW,SPARCstation-5 Typically, this name is the same as the value returned by the uname -icommand on the machine, but it need not be the same. The PLATFORM_NAME value cannot have white space and is limited to 256 ASCII characters. If it contains paren- theses, it must contain only balanced parentheses. For example. the string "foo(bar)foo" is a valid value for this keyword, but "foo(bar" is not. The other keywords in the platform identification stanza can be in any order, as long as the PLATFORM_NAME keyword is first. PLATFORM_ID The value returned by the uname -i command on the machine, for example: PLATFORM_ID=SUNW,SPARCstation-5 MACHINE_TYPE The value returned by the uname -m command on the machine, for example: MACHINE_TYPE=sun4c IN_PLATFORM_GROUP The platform group of which the platform is a member, for example: IN_PLATFORM_GROUP=sun4c The platform group name must be specified in the same file as the platform identification stanza or in the platform definition file with the name .platform/Solaris . The IN_PLATFORM_GROUP keyword is optional. A platform doesn't have to belong to a platform group. If a plat- form is not explicitly assigned to a platform group, it essentially forms its own platform group, where the platform group name is the PLATFORM_NAME value. The IN_PLATFORM_GROUP value typically equals the output of the uname -m command. IN_PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of the platform, for example: INST_ARCH=sparc This field is only required if the platform does not belong to a platform group. The INST_ARCH keyword value must be the value returned by the uname -i command on all platforms in the platform group. COMPATIBILITY
The installation program will remain compatible with the old Solaris CD format. If a Solaris CD image does not contain any platform defini- tion files, the installation and upgrade programs will select the packages to be installed based on machine type, that is, the value returned by the uname -p command. EXAMPLES
Example 1: Platform Group Definitions The following example shows platform group definitions from the .platform/Solaris platform definition file. # PLATFORM_GROUP=sun4u INST_ARCH=sparc Example 2: Platform Identification Stanzas The following example shows platform identification stanzas, which define systems that belong in a platform group, from the .plat- form/Solaris platform definition file. # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u FILES
The .platform directory must reside as /cd_image/Solaris_vers/.platform, where cd_image Is the path to the mounted Solaris CD (/cdrom/cdrom0/s0 by default) or the path to a copy of the Solaris CD on a disk. Solaris_vers Is the version of Solaris, for example, Solaris_2.9. NOTES
Typically, a platform identification stanza contains either a PLATFORM_ID or a MACHINE_TYPE stanza, but not both. If both are specified, both must match for a platform to be identified as this platform type. Each platform identification stanza must con- tain either a PLATFORM_ID value or a MACHINE_TYPE value. If a platform matches two different platform identification stanzas--one which matched on the value of PLATFORM_ID and one which matched on the value of MACHINE_TYPE , the one that matched on PLATFORM_ID will take precedence. The .platform directory is part of the Solaris CD image, whether that be the Solaris CD or a copy of the Solaris CD on a system's hard disk. SunOS 5.10 19 Nov 2002 platform(4)
All times are GMT -4. The time now is 08:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy