Performance is one of our top priorities for the m6 milestone. Now that
we have stabilized the architecture and the feature set for the 0.6
release, we want to really focus on speeding up Chandler.
We've identified 7 representative cases that we are going to track
closely, along with target times:
http://wiki.osafoundation.org/bin/view/Projects/PerformanceProject
Aparna and Olivier have CATS tests for each of the cases -- you can link
to information about each test from the table. Aparna and Olivier have
measurements from running the tests against recent releases on the
target qa hardware (also noted in the table). We're working on running
these tests regularly and posting and archiving the results.
We have uber-bugs logged for each case, which are also noted in the
table. If you are the owner of an uber-bug, your responsibility is to do
some profiling and analysis of the bug. If you find specific problems as
a result of your analysis, go ahead and log individual bugs for those
problems, assigned to an appropriate owner. Hand bugs off to others if
you get stuck, or take over an uber-bug from someone if you have some
cycles to look at performance.
We have a link on the project page for all perf related bugs, use the
'perf' keyword if you log a performance bug.
I know a bunch of you have started tackling these problems -- I'm
confident we can make a big dent in the response times, which will get
us a lot closer to a useable calendar!
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
