-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
perf: Change link-time optimization in dev and test #3441
base: staging
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favor of this as long as it doesn't have a negative impact on CI test times (in which case it would still make sense for the dev
profile).
0c33479
to
a1918e1
Compare
a1918e1
to
6a5a31b
Compare
Now that CI works again, do you mind rebasing on the latest |
6a5a31b
to
34b0f1b
Compare
@vicsn Thanks for helping with this PR. I've created a similar PR for SnarkVM as you suggested: |
Seems like the snarkOS CircleCI tests do run slower, 23 minutes on this PR instead of 17 or 18 minutes on recent PRs. Can you remove the link-time optimization for the test profile? We can keep it as the default on the dev profile. :) Also the |
This change improves the development cycle in both dev and test, when running the same command multiple times in a row. On my machine I can see improvements from minutes to seconds. For example when running `cargo run` and `cargo test`. Co-authored-by: Paul Dann <[email protected]>
34b0f1b
to
b76bb9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Motivation
This change improves the development cycle in both dev and test, when running the same command multiple times in a row.
On my machine I can see improvements from minutes to seconds. For example when running
cargo run
andcargo test
.Test Plan
Compare running this commands 3 times in a row with or without this patch
Related PRs
None