[Cosmo-dev] Cosmo performance
twl at osafoundation.org
Wed Apr 4 17:52:33 PDT 2007
At this week's preview countdown meeting we spent some time talking
about Cosmo performance. With the switch to EIM/Morse Code, there
have been a lot of changes and we don't know if the baseline
performance numbers that Jared used to size the production server
machine still hold true. Since one of the goals of the EIM/Morse
Code was to improve performance, we expect things to be better, but
we need to verify that. Also, it appears, anecdotally, that there
are parts of the Cosmo UI that should be snappier than they are.
Generally speaking, then, it seems that we probably need to get more
organized on the performance front. To that end, I'd like to make
the following proposal for getting started:
1. Have Randy and Jared work together to put together some tests that
approximate the reasoning that used by Jared's old tests. These
tests were the ones that we used for a baseline initially. Some of
these tests need to be reworked because they are DAV based, and we'll
be using EIM based syncing now.
2. Start looking a ways to measure the performance of the Cosmo UI.
In Chandler, we defined a set of use cases and a standard data set,
and measure the time it took for those operations to complete.
Things are a bit more complicated with a multi-user web app, but we
ought to be able to at least get some raw numbers for single user
responsiveness as a start. PPD is going to come up with a list of
use cases that we want to measure.
Any other ideas for areas to look at or for methodology?
More information about the cosmo-dev