Repository navigation
Add frame times from a headless WebKit build - #38
Merged
Merged
Conversation
The browser benchmark had one section, from Chrome. WebKit is the engine Safari and the Mac app use, so the doc now has a section from Playwright's headless build of WebKit 27.2 on the same machine: the canvas kept to 60 frames a second at every size up to 19,999 nodes, and SVG kept up through 1,999 nodes and dropped frames at 4,999. WebKit's clock ticks in whole milliseconds. The script now notices that, says so in the section and prints no decimal places, since "0.0 ms" would claim more than was measured. The WebKit run was driven by hand with playwright-core, which is not a dependency here; the doc says how. Still not measured: Safari itself, the Mac app's web view, Firefox, a window on a real screen, a real slow device. There is no slowed-thread pass in WebKit. The script has no tests; the Chrome section regenerates byte for byte from its saved numbers. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a second section to
docs/benchmarks-browser.md, from Playwright's headless build of WebKit 27.2 on the same M2 Max Mac.scripts/bench-browser.mjsnotices a clock that ticks in whole milliseconds, says so in the section and prints no decimal places.Not measured: Safari itself, the Mac app's web view, Firefox, a window on a real screen, a real slow device. No slowed-thread pass in WebKit, since that throttle is Chrome's. The WebKit run was driven by hand with
playwright-core, which isn't a dependency of this repo; the doc says how it was done.Tested: 527 unit tests pass locally, the leak check and the brand check pass, and the Chrome section regenerates byte for byte from its saved numbers. The script has no tests of its own.
🤖 Generated with Claude Code