Are you absolutely sure that it's the same SQL statement that produces such great differences between DBI and the command-line client? Not that a Perl-caused slowdown is out of the question, but that's always the first thing I'd double-check.
If you're getting back a ton of data from each query, then a slowdown in Perl is quite likely, especially if you're using fetchrow_array. Take a look at Speeding up the DBI, which has recipes for faster ways to fetch lots of data. However, it sounds like the slowdown happens even when no data is returned. In that case, you should do some careful DBI profiling. Most likely most of the time is spent waiting for the MySQL server's slow response..
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.