On Mon, Jan 11, 2010 at 07:43:09AM -0800, Martin wrote:
> On Jan 11, 3:35 pm, Martin <[email protected]> wrote:
> >
> > I have a daemon process which sits in DBI->execute for long periods of
> > time because it has called Oracle's dbms_alert.waitany to wait for an
> > alert. Once some procedure issues an alert the execute unblocks, we
> > find out what alert was issued and then call another procedure to
> > obtain work to do. Running Devel::NYTProf on this daemon we get > 95%
> > of the time in DBI->execute blocked in waitany :-( - this makes it
> > more difficult to home in on the areas needing attention.
> >
> > I tried setting usecputime=1 but got huge numbers like this:
> >
> > 111     1       1       2186934044s     4876069979s     
> > XXX::Data::Generation::refreshXXXLists
> 
> OOPs - ignore most of this, I was calling finish_profile instead of
> disable_profile.
> 
> Sorry for wasting your time.

You've not wasted our time. You've pointed out bugs in usecputime.
Thanks!

I've fixed one in r1013 - so the results are reasonably sane and stable,
but it's curently producing values that are *10 too big.
I'll look at that another day (or hopefully someone else will).

Tim.
-- 
You've received this message because you are subscribed to
the Devel::NYTProf Development User group.

Group hosted at:  http://groups.google.com/group/develnytprof-dev
Project hosted at:  http://perl-devel-nytprof.googlecode.com
CPAN distribution:  http://search.cpan.org/dist/Devel-NYTProf

To post, email:  [email protected]
To unsubscribe, email:  [email protected]

Reply via email to