comment on

As for how you can monitor your system resources, I would suggest lsof¹ for that. Use it with the -r option while perl processes are created and killed, and you'll know whatever stays open or not. With lsof you can also monitor sockets etc.

And you'd need 'ps' or any of the Proc modules (Proc, eg Proc::ProcessTable) to monitor memory usage. As stated elsewhere, memory cleanup depends on your OS.

hth,

Jeroen

¹ Assuming you are on *nix

Update: I also come across a mac os9 utility that lists open files

In reply to Re: How aggressively does Perl clean up when you exit()? by jeroenes
in thread How aggressively does Perl clean up when you exit()? by dave_aiello

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks