Looking at the i915 bug report, it seems like the distance field text rendering shader in Qt has too much instructions (in its HQ version) and exceeds the number of texture indirections, would be interesting to check if the distance field UbuntuShape shader has the same issue.
It would also be interesting to know how much instructions take the alternative (enabled on OpenGL ES 2 when OES_standard_derivatives is not supported) mipmapped UbuntuShape fragment shader (UC_SHAPE_MIPMAPS=1 must be set in the env to force its use). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1580792 Title: Unity8 on Intel Atoms performs poorly Status in unity8 package in Ubuntu: Confirmed 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://paste.ubuntu.com/16344427/ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1580792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
