After trying various things in various projects, here’s what has consistently worked best for me: an SQLite database file, containing data stored in YAML format, all of which data is read-only. (Modification is not allowed, because it would be impossible to keep all of the various persistent CGI-servers in sync.)
If you know that strings are likely to be used over and over again, especially in a persistent environment like mod_perl (or FastCGI), you might decide to maintain a small Cache (there are many flavors available, ready-made ...). But the principle is the same: most of the data is kept on disk, and demand-loaded, with a reasonable and adjustable cap on the number of entries that are allowed to be in memory at once.
I specified YAML because I have had “unexpected problems” that I could never quite explain with Storable. (I’d store stuff and then be unable to get it back.) So, I use this format, which also has the big advantage of being human-readable. Note also that I am rarely dealing with “every microsecond counts” performance-laden situations, so Your Mileage May Vary.™
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||