Front page | perl.perl5.porters |
Postings from September 2010
On Thu, Sep 02, 2010 at 10:34:18AM +0100, Nicholas Clark wrote: > On Thu, Aug 19, 2010 at 09:16:18AM -1000, tim.jenness wrote: > > > > On Aug 19, 2010, at 9:13 AM, Nicholas Clark wrote: > > > > > On Thu, Aug 19, 2010 at 09:10:04AM -1000, tim.jenness wrote: > > >> > > >> Great idea. Could we rebrand Devel::NYTProf so Devel::DProf would still be the perl profiler? Most people just want -d:DProf to work. > > > > > > Effectively this would eliminate acknowledgment of the contribution of the > > > New York Times back to the Perl ecosystem, which I feel would be unwise. > > > > Ok. I hadn't fully appreciated why it was called NYTProf... > > > > I suppose the next question is whether perl should ship with a profiler or not. I'm guessing "not". > > I don't see that it *needs* to. > > It's not like a profiler is a runtime requirement of production systems. > If a developer isn't able (or capable) of installing a profiler themselves > then it's a technical (or political) problem at their end, and shouldn't be > our responsibility to provide a technical solution for them. > > Devel::DProf isn't a huge technical burden sitting there being "special > biologist word". But having it be the "official" profiler, and the profiler > that everyone finds, is "Less Than Awesome", given that there *is* an > awesome profiler out there. It would be good if dprofpp simply issued a warning saying that its timings are inaccurate, and pointing people towards Devel::NYTProf. There are some things dprofpp can do that NYTProf doesn't (the -T subroutine call trace for example). I've not looked to the other profilers to see which support that well enough to recommend. Tim. p.s. Meanwhile, if anyone wants it for NYTProf it would be fairly simple to add. I'll happily assist anyone interested in working on it.Thread Previous | Thread Next