Hey perl monks around the world!
For the program that I'm writting I have to use multi-dimensional hash tables, and I have to save them to a file at the end of the program, and then include the save file at the starting of the next program.
The way I save the hash tables, is I basically create a huge perl file with lots of lines that say
$sites{"www.l33t.ca"}{'files'}{'/cgi-bin/whatever.cgi'}{'hits'} = 2034
+;

[download]

and the like. At the start of the program when I 'require' the file, it runs fine, but takes up a whooping 180 megs of RAM to do so!! The save file is only 14 megs large, and when I generate the file, the perl interpreter only uses at maximum, 20 megs of ram..
How can I 'require' this large file with out taking up so much damn memory!

Thanks a lot!

-MrOreo
www.l33t.ca

In reply to Memory Optimization by MrOreo

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.