Live data from Hacker News

Gnome / mutter triple buffering patch merged

gitlab.gnome.org

1–10 of 27 posts

Re: Gnome / mutter triple buffering patch merged

#7

Sweet! I know this patch has been cooking for a while, gosh the gitlab page takes ages to even load... Trying to look at the source... Is the whole thing less than ~1000 LOC ???

You probably got served an Anubis challenge first, doing some computations to block (LLM) scraper bots, which does slow down loading by a second or so

Re: Gnome / mutter triple buffering patch merged

#8
post #6

But can we Gilette this? Quadruple buffering? 24 buffers for the smoothest display?

I believe 3 buffers is the minimum you need for the CPU and GPU to be able to work independently and never wait for each other. Sure, one could queue up a bunch of extra frames and you'd have more margin in case of a multiple frames long stutter (at the cost of a lot of input latency), but you're typically better served avoiding multiple frames long stutters if possible. Triple buffering is, I believe, more about squeezing out all the performance you can from the hardware, not about just queuing up some number of frames which happens to be 3.

Re: Gnome / mutter triple buffering patch merged

#9
post #7

Sweet! I know this patch has been cooking for a while, gosh the gitlab page takes ages to even load... Trying to look at the source... Is the whole thing less than ~1000 LOC ???

You probably got served an Anubis challenge first, doing some computations to block (LLM) scraper bots, which does slow down loading by a second or so

Speaking of, I don't mind that in principle, but why does it linger so long on the "Success" page? It adds a handful of milliseconds of page loading and 30ms of computation, and an eternity (~seconds) of just an unnecessary delay before even starting to load the site I actually wanna go to, whys that?
Post reply on HN