-
Notifications
You must be signed in to change notification settings - Fork 13.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
Remove unneeded FIXMEs comments in search index generation #90757
Remove unneeded FIXMEs comments in search index generation #90757
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 02dd43f9b3f2e025e4e9a32c8e4578b4be6b0ff7 with merge 043642e66c714c8fbbc3729258ed12347e73ee0a... |
02dd43f
to
72ce662
Compare
Let's see if I can restart the perf check... @bors try- |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 72ce6629a5d5c2584f318bafaf08719a03c9ffae with merge 53b25d576438035cc26fbc95518b151e19ea67a3... |
☀️ Try build successful - checks-actions |
Queued 53b25d576438035cc26fbc95518b151e19ea67a3 with parent 493ea77, future comparison URL. |
Finished benchmarking commit (53b25d576438035cc26fbc95518b151e19ea67a3): comparison url. Summary: This change led to large relevant regressions 😿 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
So interestingly enough, there is no perf change, however the RSS usage reduced up to 6%. I definitely didn't expect that... |
72ce662
to
de24920
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit de2492090bfcc9b7fa663f29f2c186d7ef2cc9aa with merge 1fd792ae63cdf706c0d3029ea66fae8ea92189c3... |
☀️ Try build successful - checks-actions |
Queued 1fd792ae63cdf706c0d3029ea66fae8ea92189c3 with parent 800a156, future comparison URL. |
…d the conclusion that the code readibility wasn't worth the almost unnoticeable perf improvement
d5c45b0
to
6b3695d
Compare
Done! I updated the first comment as well as the commit message. |
Thanks :) @bors r+ rollup |
📌 Commit 6b3695d has been approved by |
…ance, r=camelid Remove unneeded FIXMEs comments in search index generation Original comment: > Instead of recreating a new `vec` for each arguments, we re-use the same. The impact on performance should be minor but worth a try. After testing it, we reached the conclusion that the code readability drop wasn't worth the almost unnoticeable performance improvement. r? `@camelid`
…ance, r=camelid Remove unneeded FIXMEs comments in search index generation Original comment: > Instead of recreating a new `vec` for each arguments, we re-use the same. The impact on performance should be minor but worth a try. After testing it, we reached the conclusion that the code readability drop wasn't worth the almost unnoticeable performance improvement. r? ``@camelid``
…ance, r=camelid Remove unneeded FIXMEs comments in search index generation Original comment: > Instead of recreating a new `vec` for each arguments, we re-use the same. The impact on performance should be minor but worth a try. After testing it, we reached the conclusion that the code readability drop wasn't worth the almost unnoticeable performance improvement. r? ```@camelid```
…ance, r=camelid Remove unneeded FIXMEs comments in search index generation Original comment: > Instead of recreating a new `vec` for each arguments, we re-use the same. The impact on performance should be minor but worth a try. After testing it, we reached the conclusion that the code readability drop wasn't worth the almost unnoticeable performance improvement. r? ````@camelid````
☀️ Test successful - checks-actions |
Finished benchmarking commit (6d38743): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Original comment:
After testing it, we reached the conclusion that the code readability drop wasn't worth the almost unnoticeable performance improvement.
r? @camelid