You can answer most of these questions yourself with some simple Google searches or a quick scan of the documentation. Here are a few answers that are perl-specific or judgment calls:
1. You can try playing with the cachesize. I think there's no way around the fact that a bunch of I/O is required.
2. You'll have to experiment to find the right cachesize. Start by giving it a lot, and then cut back. Obviously cache doesn't make difference for writes or for non-repeating workloads.
3. Use Storable.
4. BTree has always been much faster in my experience.
5. I believe there's a read-only flag.
6. Sure, as long as you use the same version of BerkeleyDB.
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.