As others have said, jamming 3G of data into 1G of ram is going to be problematic ... especially since you're doubling your amount of memory by reading the file into memory first. I would recommend:

  1. processing the file line by line
    open( my $fh, "<", $sigDataFile ) || die( "cannot open file - $!" ); while( <$fh> ) { chomp; my( $key, $value ) = split(/=/, $_); # does = need to be escaped? ... }
  2. use something like SDBM_File or GDBM_File
    use Fcntl; use SDBM_File; tie( %hash, 'SDBM_File', 'temp_file_name', O_RDWR|O_CREAT, 0666 ) or die "Couldn't tie SDBM file 'filename': $!; aborting"; open( my $fh, "<", $sigDataFile ) || die( "cannot open file - $!" ); while( <$fh> ) { chomp; my( $key, $value ) = split( /=/, $_ ); $hash{$key} = $value; ... }

-derby

In reply to Re: Memory issue while opening and reading a file by derby
in thread Memory issue while opening and reading a file by koti688

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.