| 2016-04-28 05:24:26 |
Daniel van Vugt |
description |
Software compositing of EGL clients is much slower than software clients. Even when the EGL client is allowed to render in hardware. There is something weirdly slow about our EGL texture binding compared to software textures...
Start the server with software rendering:
$ sudo env GBM_ALWAYS_SOFTWARE=1 mir_proving_server --compositor-report=log
Now start a fullscreen client (even with hardware rendering enabled) and drag the window around (so it's no longer bypassed).
Compositor performance:
7 FPS with mir_demo_client_eglflash (rendered in hardware, only rendering 1 FPS)
7 FPS with mir_demo_client_egltriangle (rendered in hardware)
30 FPS with mir_demo_client_fingerpaint (not redrawing at all)
30 FPS with 'mir_demo_client_progressbar 1' (rendered in software at 1 FPS)
30 FPS with 'mir_demo_client_progressbar 60' (rendered in software at 60 FPS) |
Software compositing of EGL clients is much slower than software clients. Even when the EGL client is allowed to render in hardware. There is something weirdly slow about our EGL texture binding compared to software textures...
Start the server with software rendering:
$ sudo env GBM_ALWAYS_SOFTWARE=1 mir_proving_server --compositor-report=log
Now start a fullscreen client (even with hardware rendering enabled) and drag the window around (so it's no longer bypassed).
Compositor performance:
7 FPS with mir_demo_client_eglflash (rendered in hardware, only rendering 1 FPS)
7 FPS with mir_demo_client_egltriangle (rendered in hardware)
30 FPS with mir_demo_client_fingerpaint (not redrawing at all)
30 FPS with 'mir_demo_client_progressbar 1' (rendered in software at 1 FPS)
30 FPS with 'mir_demo_client_progressbar 60' (rendered in software at 60 FPS)
30 FPS with 'mir_demo_client_flicker' (rendered in software at 60 FPS) |
|
