-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Cargo.toml: use codegen-units = 1 in release and bench profiles. #1192
Conversation
@matthiaskrgr, thanks for your PR! By analyzing the history of the files in this pull request, we identified @kbknapp to be a potential reviewer. |
Interesting, I've only been vaugly following the CGU changes. The pre/post benches seem to suggest the changes we decrease performance though? |
Hm, the way I read it is ns/iter => nanoseconds per iteration, so if the number gets lower we gain performance. ripgrep seemed to regress, do the build tests actually call a compiler? |
Wow, I'm not sure what exactly I was looking at, you're correct 😜 Just for SA here's a merged view of them: Merged Pre/Post Bench
And the significant changes show the build help tests like you mentioned, but also the Merged Pre/Post Bench - Only significant
I'm OK with this diff though, because the build help should only be in the failure path or "we're about to exit" path...and 0.02 ms is pretty insignificant for displaying a help message 😉 |
lto = true no longer implies codegen-units = 1 in nightly, however several CGUs may prevent some optimizations, thus force codegen-units to 1 in release and bench profiles.
cargo bench pre-patch:
cargo bench post-patch:
This change is