You would be far better off using the sar, iostat, and vmstat commands to monitor your machine. They will give you much better information about what is happening than top will. They do exactly what you want, without the overhead of starting perl from a cronjob every ten minutes (which would probably throw your stats.)
These tools are not process specific, so I would use these in combination with the output of ps. Then you could monitor the amount of ram per process.
I'm very interested to see if there are any solutions that are more Perl specific. Some of the *::proc modules look promising, but I've never used them.
If the server bogs down after a semi-regular interval you could just stop and start the server every 4 hours from a cronjob. Mercy killing it before it has a chance to kill itself.
HTH
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.