Re: Debugging script with long exec time

Don't use print for this sort of thing; use a profiler (Devel::Profile, as davidrw mentioned). Profile your program with a relatively small load (i.e. have your program print a small fraction of the map, for example). That should be enough in most cases to tell you where the bottlenecks are, without having to wait for a long run to finish.

the lowliest monk

Comment on Re: Debugging script with long exec time

Replies are listed 'Best First'.
Re^2: Debugging script with long exec time by pg (Canon) on Aug 28, 2005 at 20:57 UTC
print really has no problem here. What would be nice is to have some small scripts to analyze the log files produced. This is one of the area that perl does really good: relatively faster handing large files and has strong regexp support. With Perl it should take one no time to develop such scripts. This is the sort of thing I do quite often, and the programs that produce the log files are usually not even in Perl. What important is for the log messages to convey useful information. What to log or not to log is the key.	[reply]
Re^3: Debugging script with long exec time by samtregar (Abbot) on Aug 29, 2005 at 17:22 UTC
Many profiling tools are log-analyzers! Take a look at the output from Devel::DProf or Devel::Profiler. The file produced is essentially a specially-formated log-file of subroutine entry and exit times. The dprofpp program is a log-analyzer which reads the log and produces summary reports. -sam	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks