Add performance metrics for client-side media processing#76792
Open
adamsilverstein wants to merge 2 commits intotrunkfrom
Open
Add performance metrics for client-side media processing#76792adamsilverstein wants to merge 2 commits intotrunkfrom
adamsilverstein wants to merge 2 commits intotrunkfrom
Conversation
Add a new performance test that measures decode, resize, and encode time for generating all WordPress default sub-sizes (thumbnail, medium, medium_large, large, 1536x1536, 2048x2048) from JPEG, WebP, and AVIF source images using @wordpress/vips. This enables tracking regressions in the client-side image processing pipeline on codevitals.run, particularly for expensive formats like AVIF.
adamsilverstein
requested review from
ajitbohra,
nerrad and
ntwb
as code owners
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 7.66 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 9125d17. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23518548063
|
adamsilverstein
added
[Type] Enhancement
- Check SharedArrayBuffer availability instead of crossOriginIsolated (Document-Isolation-Policy does not set the crossOriginIsolated flag) - Add --enable-features=SharedArrayBuffer to Playwright launch args - Navigate to editor on each iteration so the import map is available - Create fresh buffer copies per resize to avoid detached ArrayBuffer - Regenerate AVIF test image for wasm-vips codec compatibility
Member
Author
Initial Performance Results (Local — Apple Silicon)Results from running 10 samples collected per format (1 throwaway warm-up excluded). Summary
Key Observations
Raw Data (10 samples each, in ms)JPEGWebPAVIFTest Environment
|
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
1 participant
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.
Summary
Adds a new performance test that measures client-side image processing time (decode → resize → encode) for generating all WordPress default sub-sizes from JPEG, WebP, and AVIF source images.
test/performance/specs/media-processing.spec.js@wordpress/vips/workerfunctions viapage.evaluate()in the editor contextmediaProcessingJpeg,mediaProcessingWebp,mediaProcessingAvifCloses #76789
Test plan