Skip to content
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

feat(ci): compile bench targets #4230

Merged
merged 1 commit into from
Mar 2, 2025
Merged

Conversation

alonh5
Copy link
Collaborator

@alonh5 alonh5 commented Feb 18, 2025

No description provided.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Collaborator Author

alonh5 commented Feb 18, 2025

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

Copy link
Contributor

@adi-yakovian-starkware adi-yakovian-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed 7 of 8 files at r1, all commit messages.
Reviewable status: 7 of 8 files reviewed, 1 unresolved discussion (waiting on @dorimedini-starkware and @Itay-Tsabary-Starkware)


crates/starknet_committer_and_os_cli/benches/main.rs line 9 at r1 (raw file):

// update it in the mentioned file. Then upload the new files to GCS with this new prefix (run e.g.,
// gcloud storage cp LOCAL_FILE gs://committer-testing-artifacts/NEW_PREFIX/tree_flow_inputs.json).

Just out of curiosity: why aren't there run instructions in this file?

@alonh5 alonh5 force-pushed the 02-18-feat_ci_compile_bench_targets branch from 43c6a96 to e91233c Compare February 25, 2025 11:09
Copy link
Collaborator Author

@alonh5 alonh5 left a comment

Choose a reason for hiding this comment

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

Reviewable status: 5 of 8 files reviewed, 1 unresolved discussion (waiting on @adi-yakovian-starkware, @dorimedini-starkware, and @Itay-Tsabary-Starkware)


crates/starknet_committer_and_os_cli/benches/main.rs line 9 at r1 (raw file):

Previously, adi-yakovian-starkware (Adi Yakovian) wrote…

Just out of curiosity: why aren't there run instructions in this file?

I don't know, but I think this is run in the CI.

Copy link
Contributor

@adi-yakovian-starkware adi-yakovian-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed 3 of 3 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @dorimedini-starkware and @Itay-Tsabary-Starkware)

@alonh5 alonh5 force-pushed the 02-18-feat_ci_compile_bench_targets branch from e91233c to 8279fa6 Compare February 25, 2025 11:13
Copy link
Contributor

@adi-yakovian-starkware adi-yakovian-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @dorimedini-starkware and @Itay-Tsabary-Starkware)

Copy link
Contributor

@Itay-Tsabary-Starkware Itay-Tsabary-Starkware left a comment

Choose a reason for hiding this comment

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

:lgtm:

But please wait for @dorimedini-starkware 's feedback as well

Reviewed 5 of 8 files at r1, 2 of 3 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @dorimedini-starkware)

Copy link

Benchmark movements:
tree_computation_flow performance improved 😺
tree_computation_flow time: [34.269 ms 34.309 ms 34.359 ms]
change: [-2.4902% -1.9420% -1.5365%] (p = 0.00 < 0.05)
Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
8 (8.00%) high mild
3 (3.00%) high severe

Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @alonh5)

@alonh5 alonh5 force-pushed the 02-18-feat_ci_compile_bench_targets branch from 8279fa6 to ae592f0 Compare February 27, 2025 08:49
Copy link

Benchmark movements:
full_committer_flow performance improved 😺
full_committer_flow time: [30.105 ms 30.142 ms 30.181 ms]
change: [-1.7136% -1.5329% -1.3519%] (p = 0.00 < 0.05)
Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
2 (2.00%) high mild
1 (1.00%) high severe

Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @alonh5)

@alonh5 alonh5 force-pushed the 02-18-feat_ci_compile_bench_targets branch from ae592f0 to f9a378b Compare March 2, 2025 09:59
Copy link
Contributor

@adi-yakovian-starkware adi-yakovian-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r4, 1 of 1 files at r5, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @alonh5)

Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware left a comment

Choose a reason for hiding this comment

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

Reviewed all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @alonh5)

@alonh5 alonh5 added this pull request to the merge queue Mar 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 2, 2025
@alonh5 alonh5 added this pull request to the merge queue Mar 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 2, 2025
@alonh5 alonh5 added this pull request to the merge queue Mar 2, 2025
Merged via the queue into main with commit 6aeeacc Mar 2, 2025
16 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants