Just an idea off the top of my head: if 'crap' is seekable, you could take a two-phased approach-- instead of storing the log entry itself in memory, just store date and the line number. At the end, you'd have a hash of parsed dates and line numbers.

After you'd built this up, you could sort by date, get each line number, seek to the line, parse and print it, and move to the next one. You'd never be storing the contents of the log file entries in memory, so your memory needs should drop a great deal.

Also, I'd investigate the Tie::* modules on CPAN. There are a number of tied hashes which handle disk-based storage.

stephen

In reply to Re: memory monster by stephen
in thread memory monster by ok

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.