Instead of caching on a cron basis cache on a request basis. The first persons visit will be slow, but then for the next X hours they will be fast, then one user is slow. If the links arn't always the same then you might even get to distribute that load over multiple users.

So then the flow is, check the database for a link, if it isn't there request it now and get the status of the links. If it is, check its expiration, if its expired then fetch it now. Now use the data in the database to render your page. (Database can be anything persistent between different connections to the web server.


___________
Eric Hodges

In reply to Re: Speeding up/parallelizing hundreds of HEAD requests by eric256
in thread Speeding up/parallelizing hundreds of HEAD requests by hacker

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.