As other had said - not a good idea, better to pass the filename or maybe record by record through a pipe?

On the memory issue, adding RAM may not help if you are only on a 32-bit machine or OS. The largest address on 32-bit is (2**32)-1, which gives a process address space of 4GB. Of this the kernel reserves a sizeable chunk - up to half (2GB) on some operating systems. Then you have the run-time libraries, perl itself, etc. using up address space. A 64-bit machine (in theory) has a limit of 16-Exobytes.

Then some operating systems (Windows) pre-allocate the heap-size at compilation time, which by default is only 1MB on Visual Studio. There are ugly hacks around this limit, but I doubt perl employs them.

Back to the drawing board I think.

In reply to Re: Reading huge file content by cdarke
in thread Reading huge file content by siva kumar

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.