Many of us deal with MySQL databases that are accessed exclusively via Perl. If performance isn't up to expectations, Perl can get blamed. To make matters worse, some of us get little or no DBA support when dealing with MySQL performance. ("You're not using Oracle|SQL Server? You're on your own.")

With that in mind, here is a no-direct-Perl-content recommendation for two Linux Magazine articles on MySQL performance (found via blakem's post about an upcoming Silicon Valley Perl Mongers talk):

There's stuff in here that can save you hours of pouring over the docs.

The author also has a presentation on Building Maintainable and Fault-Tolerant MySQL Applications with Perl.

In reply to OT: MySQL performance when the problem isn't Perl by dws

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.