Performance issues with pupil labs eye tracking

[bastianilso]

Reports of Whack-A-Mole crashing and being laggy whilst pupil labs eye tracking is activated.

@tcaruchet @mrvilix06 we should test whether we can confirm/replicate this issue on our own VR headset. For that, you will need to install the latest Pupil Capture and run it in the background: https://github.com/pupil-labs/pupil/releases/tag/v3.5

[bastianilso]

OK, so after studying the problem for a bit, this is what I know:

• We are already recording at the lowest possible resolution
• We currently record at 20FPS, recording at 10FPS helps but doesn't fix the performance issues completely.
• Disabling screen recording altogether helps, but there are still some lag spikes.

Running a profiler on Whack-A-Mole shows that the progressive paradigm is creating lag spikes because of an inefficient implementation. I'll re-write the implementation to something more performant.

[bastianilso]

Some of the lag spikes should have been addressed now through commit 9f9f1a6eef7612bb5e50baf3b09debe78048a1f1. However, the general VR performance could still be better, further profiling is needed.

[bastianilso]

From further tests with @hendrikknoche and later down in the AVA lab I noted the following:

• On my laptop, running Whack-A-Mole with eye tracking creates lag issues. The lag issues pertained even after closing Whack-A-Mole/Pupil labs. We noted that the GPU in my laptop was 86C and highly loaded, so we are worried that there is a performance drop due to heating issues - making the hardware performance less good.
• I conducted some further tests in AVALab with desktop hardware and had no performance issues running latest Whack-A-Mole and Pupil Labs.