Skip to content

ci: add target-cpu=native in bench #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Brooooooklyn merged 1 commit into main from 10-13-ci_add_target-cpu_native_in_bench

Oct 13, 2025

Merged

ci: add target-cpu=native in bench #31

Brooooooklyn merged 1 commit into main from 10-13-ci_add_target-cpu_native_in_bench

Oct 13, 2025

Conversation

Copy link

Member

@Brooooooklyn Brooooooklyn commented Oct 13, 2025

No description provided.


 ci: add target-cpu=native in bench

ce5f43e

@Brooooooklyn Graphite App

Copy link

Member Author

Brooooooklyn commented Oct 13, 2025

ci: add target-cpu=native in bench #31 Graphite 👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link

codspeed-hq bot commented Oct 13, 2025

CodSpeed Performance Report

Merging #31 will improve performances by 21.55%

_{Comparing 10-13-ci_add_target-cpu_native_in_bench (ce5f43e) with main (fff65a9)}

Summary

⚡ 2 improvements
✅ 1 untouched
⏩ 9 skipped¹

Benchmarks breakdown

Mode	Benchmark	`BASE`	`HEAD`	Change
⚡	Instrumentation	`fixtures escape simd`	31.4 ms	26.1 ms	+20.14%
⚡	Instrumentation	`rxjs escape simd`	938.1 μs	771.8 μs	+21.55%

Footnotes

9 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@Brooooooklyn Brooooooklyn merged commit 4a7dad2 into main

13 checks passed

@Brooooooklyn Brooooooklyn deleted the 10-13-ci_add_target-cpu_native_in_bench branch

October 13, 2025 04:51

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