We used the approach that you describe and it worked fine. In our case, we had a fully-normalized schema which required a six table join to get to useful data. The queries weren't terribly slow, but we were expecting lots of them.

If you want to be buzzword compliant, call your system a 'data warehouse.' Commercial database companies will sell you this same type of solution starting at six figure USD prices. I sat through a long sales pitch. As far as I could tell, your idea is the only database improvement involved in data warehousing.

I was able to get the mod_perl processes to share the memory used by the Storable data structure. This way the many http daemons didn't consume too much RAM. We had three data structures using a total of about 100M bytes of RAM.

You have to set the operating system process size limit large enough so that you don't run out of memory for the data structure.

One very minor gotcha we ran into was that the Storable data was OS dependent. It wasn't a network order problem; we just upgraded our web server OS and somehow it wouldn't read Storable data from the old OS any more. It shouldn't have had that problem, so there was probably a bug somewhere.

It should work perfectly the first time! - toma

In reply to Re: mySQL hits or Storable retrieves? by toma
in thread mySQL hits or Storable retrieves? by Hero Zzyzzx

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.