Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!usc!elroy.jpl.nasa.gov!jpl-devvax!lwall From: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Newsgroups: comp.lang.perl Subject: Re: Perl script profiler? Message-ID: <10161@jpl-devvax.JPL.NASA.GOV> Date: 29 Oct 90 23:32:22 GMT References: Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 21 In article flee@dictionopolis.cs.psu.edu (Felix Lee) writes: : I've been playing with profiling Perl scripts using the Perl debugger : hooks, and I'm wondering if I'm reinventing the wheel. Does someone : already have a profiling version of perldb.pl? Somebody (don't recall who) used to have one, but the debugger has changed enough since then that I wouldn't imagine it'd be that useful, unless they've been tracking it. : So far, I've got call graph output a la gprof, without cycle : detection. No time sampling yet; that's next. And then maybe a : statement frequency counter a la tcov. Given the great variation in the times taken by various Perl statements, I would think time sampling on a line-by-line basis would be cool. Of course, it would help if I made caller work from a signal handler... If the time it takes for the signal handler to run approaches the sample interval, however, you could get some sample tick fratricide. Larry