Comment 8 for bug 1513450

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%.