Skip to content

Conversation

@danleh
Copy link
Contributor

@danleh danleh commented Jan 15, 2026

as proposed by @kmiller68 in #258 (comment)

@danleh danleh requested a review from kmiller68 January 15, 2026 09:07
@netlify
Copy link

netlify bot commented Jan 15, 2026

Deploy Preview for webkit-jetstream-preview ready!

Name Link
🔨 Latest commit 0d19533
🔍 Latest deploy log https://app.netlify.com/projects/webkit-jetstream-preview/deploys/6968ae4747935d00099f082e
😎 Deploy Preview https://deploy-preview-260--webkit-jetstream-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

In order to avoid the CPU frequency spinning down between tests we prefetch all assets before any of the tests start in the browser.
(In the CLI/shell runner we assume all assets are on disk.)
Assets are saved in a blob URL so they can be cached on disk.
This lowers the peak memory footprint of the benchmark to a sustainable level.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this true in general (i.e., for non-JSC engines)? I.e., does the content behind a blob URL get swapped out of memory to disk before/between workloads? (My assumption so far was that the benefit of the blob URLs is to avoid another network request during the measurement window and to avoid the OS scheduler and CPU dynamic frequency scaling to affect the measurement due to I/O; not that this has a memory benefit.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant