In a nutshell, here's the issue:
- In Chrome, low FPS sometimes gives very noticeable input lag.
- This input lag only occurs when the GPU is the bottleneck. CPU lag has no effect. Specifically, it seems to be tied to fillrate.
- To try the issue for yourself, click here in Chrome or download the attached capx.
- The issue remains in Chrome Canary. In testing with Airscape, Canary actually gives far worse input lag.
- In firefox, there's no input lag. In IE, there maaaay be a tiny little bit, but that could be my imagination.
These factors lead me to assume that the input lag issue might be related to these issues.
It appears that the input lag is partially dependent on other factors not explored in my demo, as in Airscape the lag is far greater at equal FPS. I can't really confirm this easily though.
In the capx, the red line indicated reported FPS, and the green line is 1/dt. These values should be basically identical (allowing for a slight bit of variance).
One thing to note is that there's (AFAIK) no way to objectively and accurately measure input lag. Anyone know of a way?
Any thoughts about this whole issue? Any way we could get a repro to the Chrome people, and tell them that they are performing far worse than IE and firefox in this regard?
Cheers!