On Wed, Sep 08, 2010 at 07:09:05AM -0400, John P. Linderman wrote: > I am getting strange timing reports from the 4.04 Devel::NYTProf > (and earlier) release. This *is* being done on a quad-core > machine, but I am running with > > NYTPROF="clock=0" taskset 2 ... > > and it appears that the process really is staying on CPU1. > clock=0 should be getting the realtime clock: > > /usr/include/linux/time.h:#define CLOCK_REALTIME 0
Could you try with the default clock, for comparison? > The summary time on line 1118, 125s, is plausible. > > But the times on lines 1128 (433s), 1133 (432s) and 1144 (863s) > are inconsistent with the summary time on 1118, and inconsistent > with common sense (could 1144 take 900 times as long as 1143?). > > For what it's worth, these oversized times are often > close to the same (1128 and 1133) or close to even multiples > (1133 and 1144). I'm still getting useful information from > the profiler, but these large values are troubling. > Any insights? -- jpl If you run with subs=0 do the statement times become consistent? If you run the code for less iterations do the times become consistent? If so, can you identify an approximate threshold at which they jump? 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]
