On Mon, Dec 01, 2008 at 10:57:26AM -0600, Steve Peters wrote:
>
> Hi Tim,
>
> I'm starting work on a couple of things in the HACKING file and had
> some questions on a couple of items.
>
> Add time to begin and end pid markers in data file....Were you
> thinking about just adding the start and end time epochs?
Actually that one's done, so I've updated HACKING like this:
-Add time to begin and end pid markers in data file.
Add marker with timestamp for phases BEGIN, CHECK, INIT, END
(could combine with pid marker)
+Add marker with timestamp for enable_profile and disable_profile.
+The goals here are to
+a) know how long the different phases of execution took mostly for general
interest, and
+b) know how much time was spent with the profiler enabled to calculate
accurate
+percentages and also be able to spot 'leaks' in the data processing (e.g.
if
+the sum of the statement times don't match the time spent with the profiler
+enabled, due to nested string evals for example).
Hopefully that's clear enough.
> Second, for the "Pure css tooltips" are you talking about the headers
> or for each individual line?
I was thinking in terms of each line. It would act as a kind of 'help
text' but I don't think it's worth it. We have the % time tooltip now.
If we really need anything more fancy we could do with jQuery.
Meanwhile I've deleted those lines from HACKING.
[...later...] In fact I've done a long-overdue cleanup and reorg of the
HACKING file. I'd appreciate any feedback on it from anyone.
There's a project I've been meaning to ask for volunteers for...
Refactor the subs in t/20.runtests.t into a library of subs in a
t/lib/NYTProfTest.pm module. We should aim to be able to write new tests as
traditional t/*.t files that use NYTProfTest and call the subs to do the
work. This will free us from the consraints imposed by the current harness.
Specifically there's no way to directly test the data model methods.
Once refactored we'd be able to simply add
is $profile->foo, bar, 'foo should be bar';
to the .t file.
Any chance you could work on that for us Steve?
Tim.
p.s. I'd steer clear of the sub profiler and subcaller info for now as
I'm planning significant restructuring of those bits soon.
--~--~---------~--~----~------------~-------~--~----~
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]
-~----------~----~----~----~------~----~------~--~---
