"Product category pages," which are frequently called-for but rarely change, can also be managed using things like the classic Cache::Memcached. Once you've assembled the necessary (JSON?) information once, you put it the results the cache. Then, before assembling and storing it again, you query the cache first to see if it is already there. You can, if you like, even store complete HTML fragments, ready for immediate display. The "memcached" daemon automatically handles recycling of infrequently-referenced data. Just about every web-site that I am aware of uses this facility routinely for this purpose, and it can have a dramatic positive impact on performance.

In reply to Re: performance with mysql / file-caching / hash reference on demand by Anonymous Monk
in thread performance with mysql / file-caching / hash reference on demand by derion

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.