[Dev] event profiling and profile tool

[Phillip J. Eby]

At 10:32 AM 2/10/05 -0800, Ted Leung wrote:
>It would also be good to coordinate your CLI with Phillip's code for 
>profiling the unit tests...

Perhaps my tool should use 'events.prof' instead of 'profile.dat', or vice 
versa.  OTOH, if Alec's profile analysis tool accepts the filename on the 
command line, then it's of no import.  One could simply run the unit tests 
and then run the analysis tool on profile.dat to analyze the test results.

I'm certainly curious to see the profile navigation.  I seem to recall that 
somebody has written a nice GUI for analyzing Python profiling results but 
I don't remember where I saw it.  Personally I haven't had reason to do 
much with profiler data besides sort the data a couple different ways and 
display the top 10 or 20 routines by time, cumulative time, or number of calls.


>On Feb 7, 2005, at 3:16 PM, Alec Flett wrote:
>>  I just checked in a fix to:
>>http://bugzilla.osafoundation.org/show_bug.cgi?id=2329
>>
>>  This enables "Event profiling" to make performance testing much easier. 
>> You can now profile application-level events by simply going to 
>> Test->Start Profiling. All block events that get executed will be 
>> profiled to a file called "Events.prof" in the current directory.
>>
>>  The important thing is that this is specifically profiling events - 
>> i.e. it doesn't profile any noise from other actions like dragging a 
>> mouse around the ui. This makes it easy to test specific actions. For 
>> instance you can click "Start Profiling", delete an item, and then click 
>> "Stop Profiling"
>>
>>  The file is in the standard python profile format. I have also written 
>> a simple command-line profile analysis tool so you can navigate the 
>> profile output at will - but I didn't know if we had a place to check in 
>> external tools? Does anyone have any suggestions?
>>
>>  Alec