in reply to Using Devel::Profile output to know what to do next

If you've got a good feeling that your problem is database related (which you might get from watching top while something slow happens and seeing mysqld pegging the CPU, for example) then you'll get more mileage from DBI's built-in profilers than from something that only looks at the Perl side. Check out DBI::ProfileDumper for the big guns. If your app is simple enough you could also try DBI::Profile.

-sam

  • Comment on Re: Using Devel::Profile output to know what to do next