Input Lag Hierarchy

[BTRY B 529th FA BN]

What is the hierarchy of input lag? And will Blur Busters expand into these other regions?

[Q83Ia7ta]

Which input lag? Of computer components or wanna see each 120+ Hz monitor input lag?

[BTRY B 529th FA BN]

I guess from the user input POV. Or any way that would seem proper for different scenarious.

[Chief Blur Buster]

We'll be exploring input lag more over the coming months.

There's an old but good article, AnandTech: Exploring Input Lag, Inside and Out, which shows that input lag can be affected by many parts of the chain.



versus



We do plan to write a new, more modernized article (but in the Blur Busters style, and accounting for strobing technologies) similiar to this, within several months from now.

[BTRY B 529th FA BN]

Any articles over HPET via bios, and in the OS ? the OS timers play a big factor with syncing up audio, networking, and image with some games

[flood]

i dont think anyone has objective evidence that messing with hpet affects anything like what some people claim.

but generally these things are highly game/game engine dependent

all i know is that timers on windows suck

[BTRY B 529th FA BN]

I agree that there is more than what's mentioned in the Anandtech article. The timers for one, via bios e.g HPET, in OS timers, CPU behavior, etc.

[Chief Blur Buster]

I agree that there is more than what's mentioned in the Anandtech article. The timers for one, via bios e.g HPET, in OS timers, CPU behavior, etc.

I agree that a modern test is needed to uncover unexpected causes of input lag. The problem is it would take weeks and months to test thousands of combinations, so a few select tests (e.g. HPET, large vertical totals, HDMI vs DVI vs DisplayPort, etc) needs to be done, and determine how many milliseconds can be shaved off. 0.5ms there, 0.5ms there, it all adds up, 5ms total can actually make a big difference. Some input latency reducing tasks only shaves microseconds and are practically wortheless to do, but certain optimizations will impact things in an "it adds up" way.

Blur Busters is only a part time job for me (not my primary) -- it would be cool if it becomes a full time job so that i can do such kinds of tests on a more continuous and intensive basis. That said, I do plan more work on input lag related stuff -- keep tuned.

[BTRY B 529th FA BN]

I agree that there is more than what's mentioned in the Anandtech article. The timers for one, via bios e.g HPET, in OS timers, CPU behavior, etc.

I agree that a modern test is needed to uncover unexpected causes of input lag. The problem is it would take weeks and months to test thousands of combinations, so a few select tests (e.g. HPET, large vertical totals, HDMI vs DVI vs DisplayPort, etc) needs to be done, and determine how many milliseconds can be shaved off. 0.5ms there, 0.5ms there, it all adds up, 5ms total can actually make a big difference. Some input latency reducing tasks only shaves microseconds and are practically wortheless to do, but certain optimizations will impact things in an "it adds up" way.

Blur Busters is only a part time job for me (not my primary) -- it would be cool if it becomes a full time job so that i can do such kinds of tests on a more continuous and intensive basis. That said, I do plan more work on input lag related stuff -- keep tuned.

Awesome