I'm currently writing scripts to read pipe-separated values from a very large text file (160+ GB). It's necessary to process every line, but this approach: @lines = <BIGGUNFILE> is unfeasible due to memory requirements. Currently the scripts use standard line by line behavior: while(my $line = <BIGGUNFILE>) I assume that this is pretty inefficient since it should cause a lot of very small reads instead of reading the data in large chunks. I've also experimented with Tie::File, which reports that it will buffer data, but this too seems to be line by line. I only need to process each line once, so buffering this way doesn't help me much. Is there another approach in Perl wherein I can read in larger chunks of data at a time, but yet not slurp in the whole file? In other words, I'd like to read-ahead and buffer a set of X lines so that the IO would be faster...

In reply to Perl Read-Ahead I/O Buffering by jeffthewookiee

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.