I agree with the previous suggestion to test/measure. Last few weeks I start to use profiling (using Devel::DProf) and benchmarking (see benchmarking your code, this node got me started ) more and more and this helps me trying to understand where my code spends its time and where to begin speeding it up. I've never did this for mod_perl, but google found me that there is a performance tuning guide for mod_perl here, that (from the looks of it) seems to explain this rather well.

If I should have good experience with using Cache::Cache (which I actually have, very nice module), this doesn't mean that it will also speed up your code in it's specific setting (maybe your disk is 10 times as fast as mine is?).

In reply to Re: Repetitive File I/O vs. Memory Caching by eXile
in thread Repetitive File I/O vs. Memory Caching by Anonymous Monk

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.