wow, now that's what I call a profiler... I was pretty sure the issue was Perl-side because the queries don't show up in MySQL processlist (well, very occasionally they do).
NYTProf seems to be handling Class::DBI code perfectly. It's pointing to name_lc overhead (column names) which is well discussed elsewhere so I'll start reading around. thanks for the nudge in the right direction! cheers, Bob. On Thu, May 7, 2009 at 4:22 PM, Joel Bernstein <j...@fysh.org> wrote: > > On 7 May 2009, at 16:16, Bob MacCallum wrote: > >> is it more efficient? I'm running into speed problems right now as it >> happens... > > It is, but is your app code the bottleneck rather than the DB? > >> (and to make it worse DProf/dprofpp is not reporting anything useful at >> all) > > > You may want Devel::NYTProf then. DProf has been superceded. Of course, it > may not be your app at all. > > /joel >