feat: use blazediff instead of pixelmatch #37268
Closed
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.
Description
Replaces
pixelmatch
third-party with a ~20-25% faster alternative BlazeDiff. It's type-safe and uses an enhanced algorithm inspired by pixelmatch. The API and results are identical.Check Run Benchmark step.
Benchmarks
I have created a patched
playwright-core
package with@blazediff/core
instead of pixelmatch.Then, I created two repositories for benchmarking:
The benchmarks track time spent on
toHaveScreenshot
with 3 warmup iterations and 25 actual iterations.Results:
Closes #37267.