-
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
arena > Rc
for query results
#99181
arena > Rc
for query results
#99181
Conversation
r? @wesleywiser (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit baefd42 with merge 8f8b211442db131dba33b7f7f7b022ceb6eab93c... |
@rust-timer build 8f8b211442db131dba33b7f7f7b022ceb6eab93c |
Queued 8f8b211442db131dba33b7f7f7b022ceb6eab93c with parent b3f4c31, future comparison URL. |
Finished benchmarking commit (8f8b211442db131dba33b7f7f7b022ceb6eab93c): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
still think this is an improvement, even if it isn't perf relevant. |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8804161): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
The
Rc
s have to live for the whole duration as their count cannot go below 1 while stored as part of the query results.By storing them in an arena we should save a bit of memory because we don't have as many independent allocations and also don't have to clone the
Rc
anymore.