You don't post code so in generalities. It will almost inevitably be faster and more memory efficient to use system tools like gunzip, tar and rm directly than do the same in perl. Highly optimised C should beat Perl every time both in memory and speed terms. There is simply less overhead and at the end of the day things like Compress::Zlib are just wrappers on the standard system libraries and calls. Tools like top and Devel::DProf Devel::Leak and Devel::LeakTrace are available to diagnose issues.

If you post example code I am sure you will get lively interest.

cheers

tachyon

In reply to Re: How to find a memory leak - appears to be "system" calls that are responsible by tachyon
in thread How to find a memory leak - appears to be "system" calls that are responsible by naum

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.