I'm sorry, but you aren't going to make a big performance difference without rewriting your code. And that isn't the fault of DBM::Deep. If you want to make things fast, you should rewrite your code so that you sort your data, and then process your data in sorted order. That should be at least an order of magnitude faster than what you're doing now.

The physical reason is the same as the one that I described in Re: BerkeleyDB and a very large file. Seeks to disk are slow. When you're writing random records in DBM::Deep, you're forced to do a lot of seeks. But sorting can be done streaming data to and from disk. And disks are much better at that than at random access.

In reply to Re: Optimizing DBM::Deep file parameters by tilly
in thread Optimizing DBM::Deep file parameters by QM

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.