Comment 5 for bug 305630

The performance issues could also be disguised a bit better by reducing number of roundtrips required for particular use cases.

For instance, when I'm doing bug triage, my flow goes something like this:
1. Click link to load page (wait...)
2. Review bug
3. Click on an attached log to get some bit of data like which driver was used (loads quick)
4. Click back button to return to bug (wait... why doesn't this just pull instantly from the browser cache??)
5. Click on "edit description/title" (wait...)
6. Add the driver name to the title. Or paste in backtrace info. Click save (wait...)
7. Update the status/importance and leave a comment. Click save (wait...)
8. Move to next bug

If launchpad performance was improved by 20%, let's say, then my wait time would be reduced from 5 wait units to 4 wait units

But imagine instead that the workflow was adjusted so I could update the title from the main bug page rather than go to a separate page. That eliminates 2 waits (steps #5 and #6), so without changing launchpad at all, I've gone from 5 wait units to 3 wait units.