{"id":42886,"date":"2024-04-19T16:09:04","date_gmt":"2024-04-19T20:09:04","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=42886"},"modified":"2024-04-19T16:09:04","modified_gmt":"2024-04-19T20:09:04","slug":"optimizing-webkit-safari-for-speedometer-3-0","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/04\/19\/optimizing-webkit-safari-for-speedometer-3-0\/","title":{"rendered":"Optimizing WebKit & Safari for Speedometer 3.0"},"content":{"rendered":"

Alan Baradlay et al.<\/a>:<\/p>\n

\n

We made our fast JSON stringifier work for unicode characters<\/a>. We also analyzed profile data carefully and made JSON.parse<\/code> faster<\/a> than<\/a> ever<\/a>.<\/p>\n

[…]<\/p>\n

We took the release of the new Speedometer 3.0 benchmark as an opportunity to adjust inlining heuristics<\/a> based on data collected in modern Apple silicon Macs with the latest JavaScriptCore.<\/p>\n

[…]<\/p>\n

Prior to the opportunistic task scheduler, incremental sweeping in JavaScriptCore was automatically triggered by a periodically scheduled 100 ms timer. This had the effect of occasionally triggering incremental sweeping during asynchronous timing intervals, but also wasn’t aggressive enough to prevent on-demand sweeping in the middle of script execution. Now that JavaScriptCore is knowledgable about when to opportunistically schedule tasks, it can instead perform the majority of incremental sweeping in between rendering updates while there aren’t imminently scheduled timers. The process of sweeping is also granular to each marked block, which allows us to halt opportunistic sweeping early if we’re about to exceed the deadline for the next estimated rendering update.<\/p>\n

[…]<\/p>\n

Previously, we required a synchronous IPC call from the Web Process to the GPU process to determine which of the existing buffers had been released by CoreAnimation and was suitable to use for the next frame. We optimized this<\/a> by having the GPUP just select (or allocate) an appropriate buffer, and direct all incoming drawing commands to the right destination without requiring any response. We also changed the delivery of any newly allocated IOSurface handles to go via a background helper thread<\/a>, rather than blocking the Web Process’s main thread.<\/p>\n

[…]<\/p>\n

With all these optimizations and dozens more, we were able to improve the overall Speedometer 3.0 score by ~60% between Safari 17.0 and Safari 17.4.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n