Here's how I'd proceed:

  1. Open up 'top' in a window and run the script. Does mysqld stay on the CPU 100% of the time? Or is it mostly Perl? Or a mix of the two?
  2. If mysqld is eating most of the CPU time I'd bust out DBI::ProfileDumper and see what the hot queries are. Then fix them and repeat.
  3. If it's mostly Perl I'd setup Devel::DProf (unless it seg-faults, and then I'd try Devel::Profiler). That will tell you what the hot subroutines are. Fix them to work faster and repeat.

The important thing to keep in mind is that you're not trying to speed up the whole program, just the slow part. Finding the slowest part is your first priority, then you'll know where to focus your attention.

-sam

In reply to Re: Debugging script with long exec time by samtregar
in thread Debugging script with long exec time by Baz

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.