Comment 4 for bug 1564721

Yes, the arale display is 60.72Hz as shown by 'mirout'. But that's also irrelevant here as I'm using MIR_CLIENT_FORCE_SWAP_INTERVAL=0 to collect peak numbers that are independent of the physical refresh rate.

More data points for the sake of comparison (also running under Unity8 on the same phones):

MAKO:
mir_demo_client_egltriangle (about the simplest and fastest client imaginable):
[2016-04-04 10:46:20.018850] perf: : 282.60 FPS, render time 2.43ms, buffer lag 8.10ms (3 buffers)
[2016-04-04 10:46:21.023429] perf: : 332.66 FPS, render time 2.07ms, buffer lag 6.98ms (3 buffers)
[2016-04-04 10:46:22.024222] perf: : 297.70 FPS, render time 2.32ms, buffer lag 7.81ms (3 buffers)
mir_demo_client_eglplasma (a pathologically heavy fragment shader):
[2016-04-04 10:46:54.638567] perf: : 165.83 FPS, render time 4.78ms, buffer lag 13.32ms (3 buffers)
[2016-04-04 10:46:55.644152] perf: : 161.19 FPS, render time 4.88ms, buffer lag 13.79ms (3 buffers)
[2016-04-04 10:46:56.645983] perf: : 163.83 FPS, render time 4.84ms, buffer lag 13.49ms (3 buffers)

ARALE:
mir_demo_client_egltriangle (about the simplest and fastest client imaginable):
[2016-04-04 10:25:12.224706] perf: : 245.26 FPS, render time 3.24ms, buffer lag 8.98ms (3 buffers)
[2016-04-04 10:25:13.227914] perf: : 246.26 FPS, render time 3.21ms, buffer lag 8.97ms (3 buffers)
[2016-04-04 10:25:14.231324] perf: : 244.26 FPS, render time 3.25ms, buffer lag 9.02ms (3 buffers)
mir_demo_client_eglplasma (a pathologically heavy fragment shader):
[2016-04-04 10:26:35.991810] perf: : 90.81 FPS, render time 10.16ms, buffer lag 22.90ms (3 buffers)
[2016-04-04 10:26:37.001922] perf: : 91.08 FPS, render time 10.10ms, buffer lag 22.95ms (3 buffers)
[2016-04-04 10:26:38.004405] perf: : 90.81 FPS, render time 10.19ms, buffer lag 22.84ms (3 buffers)

So this shows it's possible to render super-smooth graphics in a Unity8 client on mako and arale. Only unity8-dash is letting us down.