To make testing and debugging performance issues easier, we need better reporting of how long it takes to do things, and ideally automated tests which check the speed of various operations.
... --Bob McElrath?, Tue, 05 Oct 2004 10:07:19 -0700 reply
There are two products that do this: CallProfiler? and ZopeProfiler?. CallProfiler? can time:
DTML Method Filesystem DTML Method Filesystem Page Template Filesystem Script (Python) Script (Python) Z SQL Method
CallProfiler? is most relevant for answering the question "which object on my site is taking up the most time?". CallProfiler? is included with zope (go to your Control Panel)
ZopeProfiler? uses the python Profile module and can time the same things as CallProfiler?, as well as python functions, giving source filenames and line numbers. It is relevant for determining "which parts of the Zope/ZWiki codebase are using the most time?" ZopeProfiler? is available here:
http://www.dieter.handshake.de/pyprojects/zope/#bct_sec_2.6
Thus, I don't think it's necessary to clutter the zwiki code with timing and reporting insturmentation. Instead, speed tests should be placed in the tests/ directory.
-- Bob
property change --Bob McElrath?, Tue, 05 Oct 2004 10:08:29 -0700 reply
Name: #929 need speed tests and instrumentation => #929 need speed tests
... --Simon Michael, Tue, 05 Oct 2004 13:26:25 -0700 reply
I don't mean instrumentation that duplicates those products; but in
addition to those, which require a lot of time and brainpower, we need
an easy way to see simple numbers for things like page rendering time,
linking time.
property change --simon, Thu, 07 Oct 2004 08:43:41 -0700 reply
Name: #929 need speed tests => #929 need speed tests and reporting
spambots, category? --betabug, Wed, 14 Feb 2007 01:07:41 -0800 reply
Name: #929 LUitohYzcE => #929 need speed tests and reporting
Severity: serious => wishlist
reverted spambots, put into "wishlist", not sure about which Category this went in.