Runtime Performance

• perf related bugs

Latest Data

• http://wiki.osafoundation.org/bin/view/Journal/AnthonyFrancoPerformanceTesting
• Performance tracked by Tinderbox

Targets

• see PerformanceProject
• A concise writeup on how to think about response times for users: http://www.useit.com/papers/responsetime.html.
• We're going to use our qa lab hardware as the benchmark targets.

Profiling use cases

• StartupPerformance20040803: startup time (Bug#1849)
• ViewSwitchingPerformance20040810: view switching (Bug#1850)
• DetailViewPerformance20040913: rendering a detail view (Bug#1851 may be related)
• ItemPerformance: comparison of the performance of Items vs. wxPython Python widgets
• CanvasCreateItemPerformance20040922: creating a calendar event by double clicking the canvas (Bug#1854)

• ZeroPointFivePerformanceUseCases
• ZeroPointSixPerformanceUseCases

Other studies

• ItemAccessTracing: traces of item access

Tools

• MorgenSagen wrote a quick timing module: chandler/tools/timing.py
• Donn has some notes on using HotShot

Notes:

• We've heard reports of pathologically slow cases, that we haven't seen on all developer machines. In particular, Lisa sees really slow unit test times, and Pieter was seeing 30/40 sec for some use cases that other folks see 2/3 sec. We ought to track down what is going on here.
• Goal for 0.5: get performance unit tests tracked by tinderbox (as Mozilla does). (Bug#1386)