It sounds like a "sequential write" is exactly what you need here...

Why not loop over each source file and append them to your output?

If that's not plausible for some reason, something like Berkeley DB could very well be a solution, but given the sizes you're talking about (600M of plain text, plus presumably some amount of metadata, eg. filenames, plus the overhead and index of the DB file itself), you might be running into the maximum filesize of the DB format (IIRC, DB_File's can only be 2G) in the very near future.

I assume there's a driving reason this isn't being dumped into binary records in Oracle?

Um, good luck regardless!


In reply to Re: Improving Memory Efficiency with Storable and Hashes of Scalars (code) no help at all here by baku
in thread Improving Memory Efficiency with Storable and Hashes of Scalars (code) by deprecated

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.