frameclock: Keep more history
authorBenjamin Otte <otte@redhat.com>
Tue, 9 May 2023 12:38:24 +0000 (14:38 +0200)
committerBenjamin Otte <otte@redhat.com>
Tue, 9 May 2023 14:29:41 +0000 (16:29 +0200)
commitc227493c6577cd5080f86f7bc982ed7d8f190a8b
tree91cd9b4ec53c3399ecc998f0b793258bc636123b
parent30acf00bf8e441ce6d683b975ad71b7e14f5a234
frameclock: Keep more history

Not all frames get timing info with GDK_DEBUG=no-vsync, so make sure
that even when we render tons of frames, the one frame that does get
timing info is still there when the timing info arrives.

I set it to 128 from 16 now.
This is roughly good enough to go to 5000fps from on a 60Hz monitor.
gdk/gdkframeclock.c