Richard Jones wrote I've just announced our Call Profiler product on zope.org and the zope announce list (waiting for people in different timezones to authorise them :) ( http://www.zope.org/Members/richard/CallProfiler/ for the impatient)
From my point of view, this is a critical piece for Zope - right now, trying to work out what's going on in a Zope page render is somewhat painful. We found once we'd turned this onto our production code (and Richard had made my initial vile hack actually work in a way that didn't cause bleeding from the brain) we were able to very very quickly spot a whole lot of stuff that was Just Not Doing The Right Thing.
Unfortunately, the existing python profiling stuff is at too low a level to be useful - this stuff really fills a need. Plus, if it's integrated into Zope, Richard doesn't have to spend work time on maintaining it :) Anthony
On Fri, 1 Feb 2002 14:10, Anthony Baxter wrote:
Richard Jones wrote
I've just announced our Call Profiler product on zope.org and the zope announce list (waiting for people in different timezones to authorise them :) ( http://www.zope.org/Members/richard/CallProfiler/ for the impatient)
... Richard had made my initial vile hack actually work in a way that didn't cause bleeding from the brain)
No comment ;)
Unfortunately, the existing python profiling stuff is at too low a level to be useful - this stuff really fills a need.
Although being able to tie this into the python profiler would _rock_ in terms of profiling websites that use a mix of DTML/ZPT and Python products. Even it it's just to get the timing marks where the higher level stuff like DTML/ZPT calls out to the python code (ie. getting timing for the python calls at the highest level)
Plus, if it's integrated into Zope, Richard doesn't have to spend work time on maintaining it :)
But I do have time for screenshots - there's some up on the product page now for those who have a short curiosity span :) Richard
This is really cool. The implementation looks pretty reasonable too! Definitely useful for folks doing development and wondering why their scripts take > 2 secs to run! ;-) I think this will be in many folks' toolbags soon. - C
participants (3)
-
Anthony Baxter -
Chris McDonough -
Richard Jones