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.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.