6 ms·
100ms is a long time to wait for each completion suggestion.
by cassianoleal 3y ago
100ms is a long time to wait for each completion suggestion.
- nu11ptr 3y agoI was going to say the same thing. In what world is 100ms fast on a computer? (for something not making a network round trip)
- explaininjs 3y agoThe claim isn’t that 100ms is fast, it’s that the blame for the latency lies in the engineering, not the language.
- emorning3 3y agoJakob Nielsen says that 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result... https://www.nngroup.com/articles/response-times-3-important-limits/ https://www.nngroup.com/articles/response-times-3-important-...
- Rapzid 3y agoDepends on what they are waiting for. If there were 100ms of keystroke to paint latency with typing you'd def notice it.
- Xeamek 3y agoIn gaming, delay of 100ms is huge enough for anyone besides the most casual players to notice. Obviously this are different use-cases, but wouldn't be suprised if it was big enough for people to at least notice
- emorning3 3y ago>>In gaming, delay of 100ms is huge enough for anyone besides the most casual players to notice.<< I agree. I used to play a drum beat game with my daughter and son-in-law, who are both professional musicians, and they could hit beats within a 10ms window, while I struggled to get under 100ms. But 100ms seems like a reasonable upper limit for autocomplete to me. PS: My son-in-law is a professional drummer and can't play Rush YYZ on Rock Band (just had to include this tidbit cause it'll piss him off)
- userbinator 3y agoIn absolute terms, that's a few hundred million CPU instructions.