Dash: very high latency responding to input
Bug #828582 reported by
Paul Sladen
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
High
|
Michal Hruby | ||
libunity |
Fix Released
|
High
|
Michal Hruby | ||
libunity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
High
|
Michal Hruby |
Bug Description
After an upgrade to Ubuntu 11.10 the Dash now has very high latency (500+ milliseconds) responding to user input, such as typing characters in the Dash search and seeing those letters displayed.
The GNOME HIG requires an input/feedback latency of below 100 milliseconds.
If the update is waiting on results/matches to appear it should be possible to focus on displaying the user input initially, and then waiting for further results to come in.
(In order to always meet the 100 millisecond target, it may be necessary to find ways to transparently degrade the visual quality).
Related branches
lp://staging/~mhr3/unity/background-icon-loading
- Gord Allott (community): Approve
- Sam Spilsbury (community): Approve
-
Diff: 501 lines (+285/-89)3 files modifiedplugins/unityshell/src/IconLoader.cpp (+89/-89)
tests/CMakeLists.txt (+5/-0)
tests/test_icon_loader.cpp (+191/-0)
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Michal Hruby (mhr3) |
Changed in unity: | |
milestone: | 5.0.0 → 5.2.0 |
Changed in libunity: | |
milestone: | 5.0.0 → 5.0.2 |
Changed in unity: | |
milestone: | 5.2.0 → 5.0.0 |
Changed in unity: | |
milestone: | 5.0.0 → 5.2.0 |
Changed in unity: | |
status: | Triaged → In Progress |
Changed in unity (Ubuntu): | |
status: | Triaged → In Progress |
Changed in libunity: | |
status: | Triaged → In Progress |
Changed in unity: | |
status: | In Progress → Fix Committed |
Changed in libunity: | |
status: | In Progress → Fix Committed |
Changed in unity (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in libunity (Ubuntu): | |
status: | New → Fix Committed |
Changed in libunity: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
status: | Fix Committed → Fix Released |
no longer affects: | libunity (Ubuntu Quantal) |
To post a comment you must log in.
Right now Unity itself has a pretty high timeout before sending queries to the lenses. Michal is working on improving the lens side query handling in various ways by tweaking libunity. This should make it possible to do the timeouts inside libunity, that is on the lens-side of things, allowing the lenses themselves to tweak the timeout to their needs.
Concretely, I propose:
* Lower the timeout in Unity to something very low
* Implement another timeout for dispatching LensSearch instances in libunity
* Make that timeout in libunity a writable property for Scopes to override to suit their needs