my help also included this skeleton script for KinoSearch, for which I never got any comment.
also i would look into the logs to first look where an optimization is *needed*.
what i learned about optimization is:
first look by analysing real world requests where the bottleneck is. (easy example case: maybe people are just calling "saints in our book" too often. easy solution: cache that data and remove the info about seen xy seconds ago - nobody needs that. info in an hourly scale would be enough here).
second: use munin and other tools to compare performance to see, if a specific optimization really changed something. in my app, I log the request time (the time inside the mod_perl handler) to a logfile, and let munin make a graph out of it. nice to see how that changes over time, and there's nothing better than doing an optimization and see the chart going down. and it helps to estimate future optimizations.
I don't know the current code in use, and I don't know how I can get to it. I asked for it. I would offer to at least look into it if I can see myself if there are any good places for optimization. But that's where I'm stuck. perlmonks.org is closed to the outside. So I am not able to help as I would like to.

In reply to Re^9: PerlMonks Caching by tinita
in thread PerlMonks Caching by ahmad

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.