DProf - managing the tmon.out files

[Tristan Greaves <suppressed>]

Hi,

I've got DProf working successfully on a development modperl server 
here.  It is producing tmon.out files as expected:

	proceed_id/tmon.out

Any given tmon.out file will contain all the timing information for all 
scripts run under that process ID.

However, we want to work on allowing easy profiling of individual scripts.

One way that comes to mind would be to limit the number of scripts that 
a mod_perl server will run to 1, before it reforks.  Not exactly 
efficient, but at least a single tmon.out file would contain one set of 
timing information.  A lot of files though...

In addition, we like having the single continous process up as it helps 
us spot any accidental variable persistance problems.

So, can anyone suggest any good ways of splitting up the tmon.out data 
into individual scripts?  Or is biting the bullet and running the 
"limiting" method the best way to go?

Thanks in advance,

Tris.