<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: process size in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606847#M824318</link>
    <description>Bill Hassell; Is there a way to know which processes are using shared memory on hpux 11/11i os ? &lt;BR /&gt;&lt;BR /&gt;Also, can i find the memory leakage by observing increase in memory size in glance tool ?&lt;BR /&gt;&lt;BR /&gt;best regards,&lt;BR /&gt;Shiv</description>
    <pubDate>Thu, 18 Aug 2005 23:27:50 GMT</pubDate>
    <dc:creator>Shivkumar</dc:creator>
    <dc:date>2005-08-18T23:27:50Z</dc:date>
    <item>
      <title>process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606836#M824307</link>
      <description>what is command line option with $ps command to view process size of a particular process.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Thu, 18 Aug 2005 10:24:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606836#M824307</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-08-18T10:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606837#M824308</link>
      <description>UNIX95= ps -e -o pid,vsz,args&lt;BR /&gt;&lt;BR /&gt;The UNIX95= before is important, so it uses the XPG4 syntax of the command.  Of course you can add more fields, I just added vsz (virtual set size), process ID and command.</description>
      <pubDate>Thu, 18 Aug 2005 10:28:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606837#M824308</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2005-08-18T10:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606838#M824309</link>
      <description>export UNIX95=1&lt;BR /&gt;ps -o sz | grep &lt;PID&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;"man ps" for more options. There are lot of stuff you can see with ps when XPG64 support is enabled (UNIX95=1)&lt;BR /&gt;&lt;BR /&gt;Alex.&lt;BR /&gt;&lt;/PID&gt;</description>
      <pubDate>Thu, 18 Aug 2005 10:29:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606838#M824309</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-08-18T10:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606839#M824310</link>
      <description>Here, I must agree with Simon's solution, i.e., &lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -e -o pid,vsz,args&lt;BR /&gt;&lt;BR /&gt;as exporting UNIX95 variable may have some unexpected effects on processing of other commands in the same interactive session. Let it do its job for one command and die.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 Aug 2005 10:39:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606839#M824310</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-08-18T10:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606840#M824311</link>
      <description>What XPG64 and vsz in the output stands for ?</description>
      <pubDate>Thu, 18 Aug 2005 13:10:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606840#M824311</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-08-18T13:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606841#M824312</link>
      <description>is "vsz" means RAM memory size ?</description>
      <pubDate>Thu, 18 Aug 2005 13:13:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606841#M824312</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-08-18T13:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606842#M824313</link>
      <description>vsz - virtual segment size. for details man ps&lt;BR /&gt;&lt;BR /&gt;XPG4 is a standard. Use of UNIX95 enforces the ps command conformance to XPG4.</description>
      <pubDate>Thu, 18 Aug 2005 13:14:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606842#M824313</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2005-08-18T13:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606843#M824314</link>
      <description>ps -lf&lt;BR /&gt;&lt;BR /&gt;SZ&lt;BR /&gt; The size in physical pages of the core image of&lt;BR /&gt;                          the process, including text, data, and stack&lt;BR /&gt;                          space.  Physical page size is defined by&lt;BR /&gt;                          _SC_PAGE_SIZE in the header file &lt;UNISTD.H&gt; (see&lt;BR /&gt;                          sysconf(2) and unistd(5)).&lt;BR /&gt;&lt;/UNISTD.H&gt;</description>
      <pubDate>Thu, 18 Aug 2005 13:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606843#M824314</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2005-08-18T13:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606844#M824315</link>
      <description>As far as I know XPG stands for X/open Portability Guide + version - the applications environment.</description>
      <pubDate>Thu, 18 Aug 2005 14:21:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606844#M824315</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2005-08-18T14:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606845#M824316</link>
      <description>And here's a little script for you:&lt;BR /&gt;&lt;BR /&gt;# cat processmem&lt;BR /&gt;#!/bin/sh&lt;BR /&gt;# processmem - display memory claimed by a process&lt;BR /&gt;# gwild 03192004&lt;BR /&gt;#&lt;BR /&gt;if [ $# -lt 1 -o \( $# -gt 1 -a $# -lt 4 \) ]&lt;BR /&gt;then&lt;BR /&gt;  echo "Usage:"&lt;BR /&gt;  echo "processmem \"process\""&lt;BR /&gt;  echo "Example:"&lt;BR /&gt;  echo "processmem rpc"&lt;BR /&gt;  exit 1&lt;BR /&gt;fi&lt;BR /&gt;echo " "&lt;BR /&gt;&lt;BR /&gt;PROCESS=$1&lt;BR /&gt;&lt;BR /&gt;mps=0&lt;BR /&gt;#for sz in `ps -elf | grep $PROCESS | grep -v grep | awk '{print $10}'`&lt;BR /&gt;for sz in `UNIX95= ps -e -o vsz=Kbytes -o ruser -o pid,args=Command-Line | sort -rnk1 | grep -v Kbytes | grep $PROCESS | awk '{print $1}'`&lt;BR /&gt;do&lt;BR /&gt;mps=`expr $mps + $sz`&lt;BR /&gt;done&lt;BR /&gt;#echo `expr $mps \* 4096`&lt;BR /&gt;echo "\nMemory claimed by $PROCESS: $mps Kbytes.\n"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 Aug 2005 14:31:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606845#M824316</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-08-18T14:31:21Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606846#M824317</link>
      <description>The amount of memory used by a process in HP-UX is quite complex to determine. ps (with the optional UNIX95 setting) will report the virtual memory size in Kbytes, but this is not a clear picture at all. 99% of all processes use shared text which means that only one copy of the instructions are in RAM and all copies of the same process use this one area. There is a separate stack area plus a data area which are included in the vsz calculation. &lt;BR /&gt; &lt;BR /&gt;But many processes, especially databases, use shared memory for rapid interprocess communication. Because it is shared, there is no accounting for this area in ps. You have to use ipcs -bmop to see the shared memory areas. And then there's the buffer cache which is shared by all processes that open files and read/write to them. And some processes may use memory mapped files...&lt;BR /&gt; &lt;BR /&gt;Usually, you really don't need to know much more about RAM used by processes than supplied by ps, but it isn't a complete picture. To really see RAM usage, you need to purchase the Glance product.</description>
      <pubDate>Thu, 18 Aug 2005 14:40:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606846#M824317</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-08-18T14:40:23Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606847#M824318</link>
      <description>Bill Hassell; Is there a way to know which processes are using shared memory on hpux 11/11i os ? &lt;BR /&gt;&lt;BR /&gt;Also, can i find the memory leakage by observing increase in memory size in glance tool ?&lt;BR /&gt;&lt;BR /&gt;best regards,&lt;BR /&gt;Shiv</description>
      <pubDate>Thu, 18 Aug 2005 23:27:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606847#M824318</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-08-18T23:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606848#M824319</link>
      <description>To view shared memory information use command:&lt;BR /&gt;ipcs&lt;BR /&gt;&lt;BR /&gt;To view memory segments: ipcs -m&lt;BR /&gt;To view semaphores:      ipcs -s&lt;BR /&gt;&lt;BR /&gt;You also will see he PID of the process. There are many other options to view what processes attached to these segments and when they did it. For more options you can use "man ipcs"&lt;BR /&gt;&lt;BR /&gt;Alex.</description>
      <pubDate>Fri, 19 Aug 2005 01:37:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606848#M824319</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-08-19T01:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606849#M824320</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The command "ipcs" displays information for the message queues, shared memory segments, and semaphores that are currently active in the system.&lt;BR /&gt;&lt;BR /&gt;If you user # ipcs -a option shows in details about process thier ownership, size etc.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;RAjesh</description>
      <pubDate>Fri, 19 Aug 2005 01:45:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606849#M824320</guid>
      <dc:creator>Rajesh SB</dc:creator>
      <dc:date>2005-08-19T01:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: process size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606850#M824321</link>
      <description>Memory leaks are programming errors and you will see this as particular processes continue to grow in size when they aren't suppossed to do that. How can you tell? By asking the writer of the program whether their process is supposed to get bigger without bounds. I know that is often impossible to do but if you purchased applications from a vendor, you certainly can demand to know what the normal behavior is supposed to be.&lt;BR /&gt; &lt;BR /&gt;There is no magic monitoring feature that says: Memory leak in process 1234. To see this, start be ignoring processes that do not use a lot of memort and sort the processes by size:&lt;BR /&gt; &lt;BR /&gt;UNIX95= ps -e -o vsz,pid,ppid,ruser,args | sort -rn | head -20 &amp;gt;&amp;gt; /tmp/topramusers.log&lt;BR /&gt; &lt;BR /&gt;Now run this command regularly and then check the file every day (or hour) to see what is changing. Most questions like this are related to error messages about program too bin or unable to allocate more memory. And very seldom is this a problem with a memory leak--it is a problem with 32bit programs and their memory addressing limitations.</description>
      <pubDate>Fri, 19 Aug 2005 06:33:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-size/m-p/3606850#M824321</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-08-19T06:33:07Z</dc:date>
    </item>
  </channel>
</rss>

