Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
Bug #1580792 reported by
Gerry Boland
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
High
|
Unassigned | ||
unity8 (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
(problem forked from bug 1549455)
Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU.
Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors:
http://
Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them."
Since Qt tends to perform just fine on that hardware in X11, something isn't right.
Changed in unity8 (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: performance |
tags: | added: unity8-desktop |
summary: |
- Unity8 on Intel Atoms performs poorly + Unity8 on Intel Atoms performs poorly (falls back to software rendering + more than non-Atoms do) |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: atom |
To post a comment you must log in.
I've reported https:/ /bugs.launchpad .net/mir/ +bug/1580277 to raise the GL/GLES combination problem with the Mir team