Skip to content

feat: benchmarks for new execution #1668

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.

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

Open
wants to merge 29 commits into
base: feat/new-execution
Choose a base branch
from

Conversation

Golovanov399
Copy link
Contributor

No description provided.

@Golovanov399 Golovanov399 changed the base branch from feat/new-execution to feat/new-exec-native-ext May 20, 2025 20:18
@Golovanov399 Golovanov399 added run-benchmark triggers benchmark workflows on the pr run-benchmark-e2e labels May 20, 2025

This comment was marked as outdated.

Copy link

codspeed-hq bot commented May 20, 2025

CodSpeed Instrumentation Performance Report

Merging #1668 will not alter performance

Comparing feat/new-execution-benchmarks-2 (8953fd1) with feat/new-execution (e9bc13d)

Summary

✅ 10 untouched benchmarks

@Golovanov399 Golovanov399 force-pushed the feat/new-execution-benchmarks-2 branch from 86b025f to 30e5f99 Compare May 20, 2025 23:09
@Golovanov399 Golovanov399 changed the base branch from feat/new-exec-native-ext to feat/new-execution May 21, 2025 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run-benchmark triggers benchmark workflows on the pr run-benchmark-e2e
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants