Hi,
Agree with all of those mentioned. I'd add "quitting Chandler" as I do
have sometimes the suspicion that Chandler crashed while it's actually
only slow cleaning up and quitting...
Also, there's a gradation in perf requirements so here's my "speed list":
Spiffy: actions that need to be really fast, make the app frustrating to
use otherwise:
+ Creating new items - menus, double clicking on calendar
+ Stamping and unstamping items
+ Deleting items with the Del key
Fast: actions where I can tolerate a non instant feedback as long as the
UI doesn't look broken while it updates
+ Switching between collections
+ Switching app areas
+ Overlays - activating and deactivating checkboxes
+ Dragging and dropping items to other collections or to the trash
+ Resizing Chandler window and resizing the panes
Not slow: actions where I can tolerate some slowness (but not too slow...)
+ Startup
+ Quit
Unclassified
+ Long running Chandler - after running the app for several days there
is just this general slowdown that seems to affect everything.
Also, I'd make a difference between the "complete perf" (time for the
whole action to be performed including repo commit, etc...) and the
"perceived perf" (time where the UI is unresponsive or unusable). As a
user, the "perceived perf" is what counts and there are known strategies
to hide the "complete perf" to the user for some actions (compute in the
background, avoid redraw before all new data are available, etc...).
Even when the "complete perf" is pretty good, there are things that make
the "perceived perf" look bad no matter what (e.g. redraw everything and
allow the UI to go blank for a fraction of second).
Cheers,
- Philippe
Sheila Mooney wrote:
In preparation for some of the performance work we are planning for
Chandler Alpha5, Mimi and I have made a list of the top 10 performance
issues (from our perspective) that we notice when we use the app day
to day. Mimi and I are running on older Macs some and we understand
that some of these might not be an issue on Windows or the Intel Mac.
We would like to hear from other dogfooders about which performance
use cases stand out when trying to use the app.
+ Long running Chandler - after running the app for several days there
is just this general slowdown that seems to affect everything.
+ Startup
+ Switching between collections
+ Switching app areas
+ Dragging and dropping items to other collections or to the trash
+ Creating new items - menus, double clicking on calendar
+ Overlays - activating and deactivating checkboxes
+ Resizing Chandler window and resizing the panes
+ Stamping and unstamping items
+ Deleting items with the Del key
Cheers,
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
