-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Make the arena fast path smaller #56404
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
Conversation
@bors try |
⌛ Trying commit 45da76e30802c4e272c6e82293d41142a2a8047f with merge b40fd9ad1c114049c0ef02dd1a36e93788ec0482... |
This comment has been minimized.
This comment has been minimized.
☀️ Test successful - status-travis |
@rust-timer build b40fd9ad1c114049c0ef02dd1a36e93788ec0482 |
Success: Queued b40fd9ad1c114049c0ef02dd1a36e93788ec0482 with parent d3ed348, comparison URL. |
Finished benchmarking try commit b40fd9ad1c114049c0ef02dd1a36e93788ec0482 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The perf-results mostly look like noise (except for cc @rust-lang/wg-compiler-performance |
The results doesn't look like noise though. The whole point of the arena is performance. We should just use |
This is also a nice size optimization. It brings the fast path for allocating an
to:
|
I can see the first change making sense but why change from |
@michaelwoerister It avoids the instructions realigning the bump pointer by keeping it always |
Might make the |
I'm still not convinced that there are performance gains here. Compare this to a perf.rlo run from a few days ago where I accidentally benchmarked to equivalent versions of the compiler (so we know what we see is noise): Except for |
I agree that the result are probably just noise, with the possible exception of |
If you remove the |
r? @michaelwoerister