Sponsored Content
Full Discussion: Understanding prstat
Operating Systems Solaris Understanding prstat Post 302792481 by abohmeed on Wednesday 10th of April 2013 01:01:20 PM
Old 04-10-2013
Could you please shed some light on that "shared memory" thing because i don't fully understand this term. Does it mean that memory is allocated to whatever process is needing it and when when other processes need this memory they are kept in the queue until free? and does that affect performance?
 

10 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. Shell Programming and Scripting

prstat in shell

Hello, How can I do to use prstat command in a korn-shell ? Thanks a lot. Rgds. (4 Replies)
Discussion started by: madmat
4 Replies

3. Shell Programming and Scripting

prstat problem

This will be a smaple output for my prstat -t NPROC USERNAME SIZE RSS MEMORY TIME CPU 43 root 249M 62M 1.5% 33:50:01 0.1% 12 oadmin 1396M 862M 22% 0:06:49 0.1% 2 acne 3960K 3176K 0.1% 0:00:00 0.0% 4 essagent 10M 7456K 0.2% 0:00:00 0.0%... (6 Replies)
Discussion started by: vivsiv
6 Replies

4. Solaris

understanding the prstat log

Can some one please explain what does the memory part mean in the prstat logs? NPROC USERNAME SIZE RSS MEMORY TIME CPU 61 oracle 36G 33G 71% 109:44:26 12% 89 cemsbin 12G 9523M 20% 195:02:41 11% 2 adm 273M 199M 0.4% 47:05:42 2.3% 89 root ... (9 Replies)
Discussion started by: dipashre
9 Replies

5. Solaris

prstat O/P

Good Evening everyone, I am confused about prstat O/P as it shows memory values which are different from actual value.Below is the O/P of prstat command and swap commands. NPROC USERNAME SIZE RSS MEMORY TIME CPU 48 root 2113M 1590M 1.2% 45:09.39 32% 31 daemon ... (7 Replies)
Discussion started by: vvpotugunta
7 Replies

6. Shell Programming and Scripting

prstat output in GB

Hi, Is there any way by which the unit of size and rss will be only GB while I am running the prstat command? (2 Replies)
Discussion started by: King Nothing
2 Replies

7. Shell Programming and Scripting

prstat

hi all, am writing a ksh script on solaris 9 to get the number of threads taken by a process. am using the prstat -p command to do this. output i get is : :"/export/home/user" > prstat -p 25528 | cut -f2 -d/ NLWP 203 Total: 1 processes, 203 lwps, load averages: 2.58, 3.24, 3.62... (2 Replies)
Discussion started by: cesarNZ
2 Replies

8. 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

9. Shell Programming and Scripting

prstat output

hi all, have a ksh script where i am doing a prstat -m -u osuser 1 1 >> $FILE_NAME but for some reason it only writes 15 lines wheres when i run the same command manually from command prompt it prints out 60 lines. why is it not writing the full 60 lines to the file ?? ta. (1 Reply)
Discussion started by: cesarNZ
1 Replies

10. Shell Programming and Scripting

prstat from ptree ...

Hi, I know how to figure out the list of PID from my application name : ptree `pgrep MyApp` | awk '{print $1}' But I dont know how to pipe it for prstat -p <pidlist> ptree `pgrep MyApp` | awk '{print $1}' | prstat -p ??? I would like to monitor every ptree PID from my application. ... (4 Replies)
Discussion started by: RickTrader
4 Replies
MEMSTAT(1)						     Linux Programmer's Manual							MEMSTAT(1)

NAME
memstat - Identify what's using up virtual memory. SYNOPSIS
memstat [-w][-p PID] DESCRIPTION
memstat lists all accessible processes, executables, and shared libraries that are using up virtual memory. To get a complete list memstat has to be run as root to be able to access the data of all running processes. First, the processes are listed. An amount of memory is shown along with a process ID and the name of the executable which the process is running. The amount of memory shown does not include shared memory: it only includes memory which is private to that process. So, if a process is using a shared library like libc, the memory used to hold that library is not included. The memory used to hold the exe- cutable's text-segment is also not included, since that too is shareable. After the processes, the shared objects are listed. The amount of memory is shown along with the filename of the shared object, followed by a list of the processes using the shared object. The memory is listed as the total amount of memory allocated to this object throughout the whole namespace. In brackets also the amount that is really shared is listed. Finally, a grand total is shown. Note that this program shows the amount of virtual (not real) memory used by the various items. memstat gets its input from the /proc filesystem. This must be compiled into your kernel and mounted for memstat to work. The pathnames shown next to the shared objects are determined by scanning the disk. memstat uses a configuration file, /etc/memstat.conf, to determine which directories to scan. This file should include all the major bin and lib directories in your system, as well as the /dev directory. If you run an executable which is not in one of these directories, it will be listed by memstat as ``[0dev]:<inode>''. Options The -w switch causes a wide printout: lines are not truncated at 80 columns. The -p switch causes memstat to only print data gathered from looking at the process with the gicen PID. NOTES
These reports are intended to help identify programs that are using an excessive amount of memory, and to reduce overall memory waste. FILES
/etc/memstat.conf /proc/*/maps SEE ALSO
ps(1), top(1), free(1), vmstat(8), lsof(8), /usr/share/doc/memstat/memstat-tutorial.txt.gz BUGS
memstat ignores all devices that just map main memory, though this may cause memstat to ignore some memory usage. Memory used by the kernel itself is not listed. AUTHOR
Originally written by Joshua Yelon <jyelon@uiuc.edu> and patched by Bernd Eckenfels <ecki@debian.org>. Taken over and rewritten by Michael Meskes <meskes@debian.org>. Debian 01 November 1998 MEMSTAT(1)
All times are GMT -4. The time now is 09:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy