Experiment: New fmt::Arguments implementation (2021)#84823
Experiment: New fmt::Arguments implementation (2021)#84823m-ou-se wants to merge 2 commits intorust-lang:masterfrom
Conversation
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
⌛ Trying commit 3259ba1 with merge f585107e5e534511ae54ad991ac429aef3b99ebd... |
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
⌛ Trying commit e89626f with merge 9d649c160c564fa8820680f3132796f90912466b... |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
☀️ Try build successful - checks-actions |
|
Queued 9d649c160c564fa8820680f3132796f90912466b with parent 89ebad5, future comparison URL. |
|
Finished benchmarking try commit (9d649c160c564fa8820680f3132796f90912466b): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
|
Up to 9.3% improvement for helloworld-opt incr-patched and up to 8.4% regression for webrender-wrench-check incr-patched. For full builds many regressions up to 6.8% and some improvements up to 2.0%. |
|
Yeah these results are all over the place. Not sure why. fmt::Arguments was reduced from 6 pointers to 2 pointers in size, and the output of format_args!() didn't really change much in complexity. |
|
Going to go ahead and close this since it seems like it's not likely to receive much further attention. |
Just testing some incomplete idea.