Re: dprofpp - understanding the output

Those are the BEGIN blocks in those modules. By the way, when profiling something that uses DBI, you almost always want to profile wallclock time, not CPU time. Use the -r flag to dprofpp.

Comment on Re: dprofpp - understanding the output

Replies are listed 'Best First'.
Re^2: dprofpp - understanding the output by kyle (Abbot) on Jul 20, 2007 at 17:33 UTC
when profiling something that uses DBI, you almost always want to profile wallclock time Yes. It's also handy to use the DBI's own profiling code (invoked by setting a `DBI_PROFILE` environment variable). See DBI::Profile.	[reply] [d/l]
Re^2: dprofpp - understanding the output by Joost (Canon) on Jul 20, 2007 at 20:03 UTC
Note that when you "use" a module, loading, compiling & importing the module and executing the immediate code in the module gets processed during a BEGIN block in the caller. See also use. In other words, a lot of the time in the OP's profiling data is probably spent loading & initializing modules. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]