Sometimes Perlish solutions are more about stepping back and strategizing than anything else. I don't know much about your site, but is it possible to anticipate what pages will be requested, to hit them and then to cache the results for a period of time such that multiple users could benefit from a single fetch? Even if only one user could benefit, at least that puts you in control of when fetches are being done, rather than doing them real-time on demand.

How long before a cached result becomes stale is one of the big questions to whether this sort of strategy could work to your benefit, but without knowing more info, it seems like something you could consider.


Dave

In reply to Re^3: CGI and Threads by davido
in thread CGI and Threads by cyber-guard

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.