Based on rsiedl's description of the setup, it sounded like there was already a rational basis for segmenting the data into distinct tables, and the usage pattern for the data didn't seem to motivate full integration into a single huge table (rows fall into large independent sets, and queries never need to span across sets).

I'll confess that I'm no jedi when it comes to optimizing an RDB through careful crafting of table layout, query construction and indexing. This probably explains why I can imagine situations where the conditions on an oft-needed query might not lend themselves easily to effective indexing, and reducing the size of a full-table scan would be worthwhile.

In reply to Re^5: Speed of MySQL DBs by graff
in thread Speed of MySQL DBs by rsiedl

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.