As you describe it, the (memory) bottle neck is when you start processing the array. Shifting off the elements at each iteration will save memory - but the memory isn't released back to the OS - it just means that it takes longer before Perl needs to ask more memory from the OS. So, wether it helps to speed up the program depends on what else you do in the program - if you won't use much more memory, there's little gain. OTOH, shift is a fast operation, so there's not much reason to not do it.

If however you are looking for a real performance boost, look into an algorithm that doesn't require the entire array to exist at one time. The fact you don't need an element anymore after you process it suggests you may not need all the elements before processing the first one either.

Abigail

In reply to Re: performance of huge array looping by Abigail-II
in thread performance of huge array looping by kommesel

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.