Looking at callgrind output on the desktop, there are no obvious mir hotspots we could single out and optimize. It's similar to the output of perf, in that quite a bit time is just spent in the GL + dri driver code.
One more point, using the interactive governor (which we should be defaulting to anyway) the N4 cpu usage reported by top is around 23%. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
