unity8-dash 100% CPU usage when scrolling

Bug #1494795 reported by dinamic
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Triaged
High
Michał Sawicz
unity8 (Ubuntu)
Triaged
High
Unassigned

Bug Description

i'm on meizu mx4 (stable channel -r4), when i scroll up and down on the apps scope, unity8-dash is at 100%CPU usage. i have 60 apps installed and the apps scope is laggy. another annoying thing is that random icons are missing when i scroll fast up and down. i can see the random icons load.

Tags: performance
affects: canonical-devices-system-image → unity8 (Ubuntu)
summary: - unity8-dash 100%CPU usage, apps scopes laggy
+ unity8-dash 100% CPU usage, apps scopes laggy
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: unity8-dash 100% CPU usage, apps scopes laggy

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity8 (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed unity8-dash is weirdly inefficient. The good news is the CPU usage is so pronounced that some simple profiling should explain what the problem is.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please keep this bug about the 100% CPU. The lag is actually a combination of multiple different issues, in QtMir/Mir/Unity8/USC.

summary: - unity8-dash 100% CPU usage, apps scopes laggy
+ unity8-dash 100% CPU usage
tags: added: performance
summary: - unity8-dash 100% CPU usage
+ unity8-dash 100% CPU usage when scrolling
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed this bug is still occurring in the latest xenial devel-proposed images.

On a related note, I've been experimenting to observe how the phone behaves when you remove vsync (not for production use, but to take measurments). One interesting finding from that is we're still spending a very high amount of time rendering the unity8 dash, so much so that it's barely faster than with vsync enabled (mako), or in some cases still not fast enough to reach 60Hz (arale). So optimizing the dash, QML, Qt and fixing bugs like this looks like it might be on the critical path for phone performance.

Changed in unity8 (Ubuntu):
importance: Undecided → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Possibly related: bug 1564721

Changed in canonical-devices-system-image:
assignee: nobody → Michał Sawicz (saviq)
importance: Undecided → High
status: New → Confirmed
Michał Sawicz (saviq)
Changed in canonical-devices-system-image:
status: Confirmed → Triaged
Changed in unity8 (Ubuntu):
status: Confirmed → Triaged
assignee: nobody → Albert Astals Cid (aacid)
Revision history for this message
Albert Astals Cid (aacid) wrote :

There's various reasons for this, one of the reasons for some scopes is https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604025

Revision history for this message
Albert Astals Cid (aacid) wrote :

Another problem is UITK's image path interception https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604029

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Unless mobile and desktop have dramatically different code paths, we can possibly merge this with bug 1604029 now, which has a fix. Because 23% CPU on a desktop is likely the same thing as 100% on a phone.

If you assume both mobile and desktop share the same code then probably one of the following has to be true:
  1. Bug 1604029 was a duplicate of this one and has solved it; or
  2. This bug has gone away mysteriously.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

or
   3. There was something using much more than 23% CPU which we ignored :)

The answer will become clearer after the fix for bug 1604029 hits devices.

summary: - unity8-dash 100% CPU usage when scrolling
+ unity8-dash 100% CPU usage when scrolling or resizing
summary: - unity8-dash 100% CPU usage when scrolling or resizing
+ unity8-dash 100% CPU usage when scrolling
Revision history for this message
Albert Astals Cid (aacid) wrote :

Ok, you're misunderstanding the 23% CPU time number i wrote there, it meant "23% of the CPU time spent by the program", not that it is using 23% of the CPU itself.

There's a bit more detailed description of where the CPU usage of vertically scrolling comes from at https://docs.google.com/document/d/1Gf2bRxNc_8R_620o_9J1EZ6GWLGOmNBrvNfLRTLwrqc/edit

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ah OK, thanks. You need to be very careful with wording in those cases. I've changed the title of bug 1604029 to clarify.

Changed in unity8 (Ubuntu):
assignee: Albert Astals Cid (aacid) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.