Re:Measuring keyboard-to-photon latency with a light sensor
by ubercow13 on Sunday May 31, 2020 @12:17PM
(#23370516)
Comparing 'Chrome html input' to VS Code in the article, it seems like Chrome is capable of rendering typed text with low latency. This seems to imply that the high input latency in VS Code can't be due to low level GPU and rendering pipeline issues brought about by electron, and must instead be due to processing VS Code is itself doing every time you type (syntax highlighting, semantic things, layout?). If this is true it seems unlikely monitor refresh rate or gsync could help.
[ Parent
| on HN ]
Re:Measuring keyboard-to-photon latency with a light sensor
by londons_explore on Monday June 01, 2020 @01:40AM
(#23375717)
Chrome has effectively a 1 frame latency. First the event fires for a keypress, and later the compositor decides it's time for a new frame, which will include the effects of that keypress.