Hi Monks!

This small snippet is just an example of what your mighty
/proc filesystem in Linux can do for you. They report the
vsize (allocated virtual memory) of your perl process inclusive
all data it allocated and the number of pages your process
uses.

Find out the VMEM (virtual memory) size your current perl
process has grabbed, find out the number of pages it uses:
  open( STAT , "</proc/$$/stat" ) or die "Unable to open stat file";
  @stat = split /\s+/ , <STAT>;
  close( STAT );

  print sprintf "Vsize: %3.2f MB\n", $stat[22]/1048576;
  print "RSS  : $stat[23] pages\n";

[download]
Of course you may just get the byte number for vsize and so
on. These values help me a lot to prevent the process from
trashing (watching these values relatively to /proc/meminfo).
There is more to this /proc/your_proc_id/stat thing. Just
check out 'man 5 proc'.

In reply to /proc Gimmicks (Linux specific) by PetaMem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.