News for hackers. Stuff that matters.
Re:Modern software performance is firmly in its “beyond paro... by seba_dos1 on Wednesday March 29, 2023 @11:32AM (#35358716)
Because most screens are running at 16.6ms refresh rate, composition is vsynced and windows are double-buffered at multiple stages in the whole display pipeline to avoid tearing and other kinds of artifacts. You're naturally going to have 2-3 frames of latency unless you try really hard to avoid it with advanced frame scheduling that won't be worth employing for an office application. You usually optimize application rendering for smoothness (no frame drops, no artifacts, consistent 60 FPS) rather than latency, and doing one usually hurts the other.
Re:Modern software performance is firmly in its “beyond paro... by amoss on Wednesday March 29, 2023 @01:03PM (#35360061)
Ah, ok so you are considering the latency rather than the throughput. I was thinking that being able to perform the update within 16.6ms should not be too hard - there is a sibling comment about SSD latency but the working set should fit in RAM.

Sure, so there will be latency, maybe 4-5 frames with input lag. But this is normally bearable in a game so I'm guessing that it would work fine for an office app. It would be difficult to remove, but 80ms response time from an application that can always hit its 16.6ms deadline should be workable.

Re:Modern software performance is firmly in its “beyond paro... by seba_dos1 on Wednesday March 29, 2023 @01:25PM (#35360367)
We're talking about switching between conversations, latency is all that matters :)
Re:Modern software performance is firmly in its “beyond paro... by ehaliewicz2 on Wednesday March 29, 2023 @06:29PM (#35364763)
This seems like needless pedantry. The computer should be able to easily do it in 16ms or less. Add on the 16ms or whatever of extra latency for the mouse and display, and it's fine.