I've encountered this before. I have a solution, but it is
far from optimal. I ended up trading memory for CPU utilization.
In my instance, this tradeoff worked well, but based on how
you're using and accessing the data it may not be apropriate to you.
With that disclaimer out of the way:
What I did was searlize all the objects in the hash. When
I needed to access them I re-inflated them into full-fledged
objects. Depending on your data you could even use on-disk storage
(like a tied dbm file, or even a real DB) for the objects; only
pulling into memory the ones you need. When I used this technique
I did not go as far as to use on-disk storage for the
data elements, but by just searilizing them I cut down
my memory usage by nearly %75; of course, it took about twice
as long to run. I used Storable, but there are several
other good perl modules out there that can searilize your objects.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.