[Webkit-unassigned] [Bug 284823] New: [Win] requestAnimationFrame can't reach display refresh rate

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 17 09:16:57 PST 2024


https://bugs.webkit.org/show_bug.cgi?id=284823

            Bug ID: 284823
           Summary: [Win] requestAnimationFrame can't reach display
                    refresh rate
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Windows 11
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Template Framework
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ian.grunert at gmail.com

Test site: https://www.mobzystems.com/online/measure-browser-animation-speed/

WebKit MiniBrowser gets about 35fps on this test, well below the 60fps on Firefox. SetTimer / WM_TIMER used within RunLoopWin has a granularity of about 10ms and is likely bottlenecking our ability to hit 60fps on requestAnimationFrame.

Chromium uses MsgWaitForMultipleObjectsEx in it's run loop to deal with this limitation: https://source.chromium.org/chromium/chromium/src/+/main:base/message_loop/message_pump_win.cc;l=467-485?q=WM_TIMER&ss=chromium%2Fchromium%2Fsrc

Adopting something similar in WebKit's RunLoopWin would improve performance for WebGL apps such as https://webglsamples.org/aquarium/aquarium.html

Seems like bug 211711 may be related.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241217/f6c6c2e3/attachment-0001.htm>


More information about the webkit-unassigned mailing list