ubuntu-phone team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

This also helps a lot:
   restart unity8 QML_NO_TOUCH_COMPRESSION=1

Although until now I've been testing performance using "flings", so as 
to work around that issue which is described here:
https://bugs.launchpad.net/qtmir/+bug/1486341

- Daniel


On 14/08/15 23:39, Alberto Aguirre wrote:
> On Fri, Aug 14, 2015 at 4:05 AM, Oliver Grawert <ogra@xxxxxxxxxx
> <mailto:ogra@xxxxxxxxxx>> wrote:
>
>
>     usually android phones use the interactive or the userspace cpufreq
>     governor (the latter with a userspace daemon) with frequency scaling
>     directly tied to input/user events, we leave setting up this stuff to
>     the container under the assumption that the android setup already does
>     the best with the HW.
>
>
> I think that's the wrong assumption. They will be tuned for a typical
> android workload;
> I believe its worth looking into tweaking these governors to
> match Ubuntu's usage patterns and expected performance.
>
>
>     i bet you will see the frequency go up and down along when checking the
>     above again while watching it (which, along with the fact that someone
>     should probably look into optimizing it for our use-cases, probably also
>     points out that we are not doing enough of our processing in the GPU).
>
>     ciao
>              oli
>
>
>     --
>     Mailing list: https://launchpad.net/~ubuntu-phone
>     Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>     <mailto:ubuntu-phone@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~ubuntu-phone
>     More help   : https://help.launchpad.net/ListHelp