MLDBM is bound to slow down your script somewhat, due to the nature of what it's doing for you (storing your multi-level datastructures on disk). If you read the WARNINGS section of the MLDBM doc, you'll see that it does matter how you access your MLDBM-tied hashes.

In particular, this means that instead of doing this:

for my $k (keys %{$h{something}}) {
    print $h{something}{$k}[0]{foo}{bar};  # FETCH _every_ time!
}

[download]

.. you're better off doing this, to avoid FETCH-ing the top-level value every time:

my $root = $h{something};                  # FETCH _once_
for my $k (keys %$root) {
    print $k->[0]{foo}{bar};
}

[download]

(Examples taken from MLDBM doc)

You might want to review your code for these kinds of situations.

HTH

--
3dan

In reply to Re: MLDBM slows down my script by edan
in thread MLDBM slows down my script by js1

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.