Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the devel-nytprof CPAN distribution.

Report information
The Basics
Id: 40593
Status: resolved
Priority: 0/
Queue: devel-nytprof

People
Owner: Nobody in particular
Requestors: adamk [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Time terminology is not consistent
Download (untitled) / with headers
text/plain 843b
Trying out Devel::NYTProf for the first time (on Win32 yay!) the thing that sticks out the most is that the way time is described is not consistent across the entirety of the reports. The most obvious case is that the coloured time boxes are all described in scientific notation seconds, even when very low. For example. 0.50000 1.1e-05 And yet in the text strings which describe inbound and outbound calls to a line or function, it is described in unit terms. # spent 93.8ms making 43497 calls to Scalar::Util::blessed, avg 2µs/call When comparing the time spent called to other functions with the times on the left, it's hard to make a direct comparison, because of the completely different notation. Please find a way to reconcile these differences... Personally, I would probably prefer to have the latter form used consistently.
Subject: Re: [rt.cpan.org #40593] Time terminology is not consistent
Date: Sun, 2 Nov 2008 22:21:32 +0000
To: Adam Kennedy via RT <bug-devel-nytprof [...] rt.cpan.org>
From: Tim Bunce <Tim.Bunce [...] pobox.com>
Download (untitled) / with headers
text/plain 1.1k
On Sat, Nov 01, 2008 at 09:58:03AM -0400, Adam Kennedy via RT wrote: Show quoted text
> > Trying out Devel::NYTProf for the first time (on Win32 yay!) the thing > that sticks out the most is that the way time is described is not > consistent across the entirety of the reports. > > The most obvious case is that the coloured time boxes are all described > in scientific notation seconds, even when very low. For example. > 0.50000 > 1.1e-05 > > And yet in the text strings which describe inbound and outbound calls to > a line or function, it is described in unit terms. > > # spent 93.8ms making 43497 calls to Scalar::Util::blessed, avg 2µs/call > > When comparing the time spent called to other functions with the times > on the left, it's hard to make a direct comparison, because of the > completely different notation. > > Please find a way to reconcile these differences... > > Personally, I would probably prefer to have the latter form used > consistently.
I agree. I had hoped to do that before the release but the ball-of-mud that is Devel::NYTProf::Reader got in my way. It badly needs to be refactored to death: http://code.google.com/p/perl-devel-nytprof/source/detail?r=578 Tim.
Fixed for next release.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.