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
Implement Span using interned pointers. #98352
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit a64683e with merge 9bff361f50324ff1c05a052e3c1445138c2c5a64... |
span_data | ||
} else { | ||
let span_data = Box::new(span_data); | ||
let span_data = Box::leak(span_data); |
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.
This is a memory leak. Please store references to keep it alive in SpanInterner
instead.
☀️ Try build successful - checks-actions |
Queued 9bff361f50324ff1c05a052e3c1445138c2c5a64 with parent 72fd41a, future comparison URL. |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (9bff361f50324ff1c05a052e3c1445138c2c5a64): 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. 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit d9d06b70ef21bab452c8fc7b9f53a718087e9b38 with merge 3533a2c0414956096ff0b680f6b87ebd1d1b5b45... |
💔 Test failed - checks-actions |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 412b9bb with merge 876335f4021704ed4de5e1b38307b9ea20406a99... |
☀️ Try build successful - checks-actions |
Queued 876335f4021704ed4de5e1b38307b9ea20406a99 with parent 10f4ce3, future comparison URL. |
Finished benchmarking commit (876335f4021704ed4de5e1b38307b9ea20406a99): 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. 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 |
Perf only
r? @ghost