In the engineering meeting this afternoon we refined the scenarios that we are mostly concerned about improving for Preview. They are listed at the top of http://wiki.osafoundation.org/Projects/PerformanceProject. We also set new acceptable targets for these scenarios - and we really do think these would become blockers if we don't reach them.
We noted two additional tests we want to have: * Quick entry in Dashboard with 3k * Triage in Dashboard with 3k Once we reach acceptable values on all platforms for a given scenario, we can stop work on that scenario and concentrate on improving the others. Of course, we still care about regressions, and based on feedback may pursue other performance cases as well. It was also requested that these scenarios be moved to the top of the performance reports on Tinderbox, and that the coloring be changed as follows: * Entries in the absolute values columns will get green background if the value is under ideal time, orange if under acceptable time, and red otherwise. Note: I also use std.dev such that I won't change the color for the better unless it is under the target-std.dev. * Entries in the delta columns will get colored borders. The rules haven't changed for these: green means it got better, orange slightly slower, and red much slower. If you have any feedback regarding the scenarios, targets or reports, please let us know. Oh, we are working on getting a more representative data set about real world usage. PS. I have some feedback regarding the new coloring scheme. I don't like the switch to make absolute values have colored background and deltas have borders. The new way of course makes it easy to see at a glance what the current situation is, but I am more interested in seeing the changes at a glance. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
