Skip to content
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

GC the Stacked Borrows allocation history #3083

Merged
merged 1 commit into from
Sep 25, 2023
Merged

Conversation

saethlin
Copy link
Member

This handles the biggest contributor to #3080

The benchmark that this adds demonstrates the memory improvement here, but our benchmark setup doesn't record memory usage, and hyperfine doesn't support emitting memory usage stats. I ran this benchmark manually with /usr/bin/time -v cargo +miri miri run 🤷

@oli-obk
Copy link
Contributor

oli-obk commented Sep 25, 2023

Did this affect performance in your tests?

@saethlin
Copy link
Member Author

Nope, this seems to have no impact on runtime. But it halves the memory usage of the new benchmark.

@oli-obk
Copy link
Contributor

oli-obk commented Sep 25, 2023

@bors r+

@bors
Copy link
Contributor

bors commented Sep 25, 2023

📌 Commit d7f02d2 has been approved by oli-obk

It is now in the queue for this repository.

@bors
Copy link
Contributor

bors commented Sep 25, 2023

⌛ Testing commit d7f02d2 with merge 914a10d...

@bors
Copy link
Contributor

bors commented Sep 25, 2023

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing 914a10d to master...

@bors bors merged commit 914a10d into rust-lang:master Sep 25, 2023
7 checks passed
@saethlin saethlin deleted the gc-history branch September 25, 2023 16:00
bors added a commit that referenced this pull request Mar 18, 2024
make 'invalidate' benchmark shorter

This is currently by far the slowest benchmark in our suite, taking >9s, when the second slowest takes 2.7s. So let's speed this up to 2.3s, making it still the second-slowest in the benchmark suite.

`@saethlin` any objections? Also, why is this called "invalidate"? It got added in #3083 but I can't figure out the point of that name even after looking at the PR.^^ There should be a comment in the benchmark explaining what it is testing.
RalfJung pushed a commit to RalfJung/rust that referenced this pull request Mar 23, 2024
make 'invalidate' benchmark shorter

This is currently by far the slowest benchmark in our suite, taking >9s, when the second slowest takes 2.7s. So let's speed this up to 2.3s, making it still the second-slowest in the benchmark suite.

`@saethlin` any objections? Also, why is this called "invalidate"? It got added in rust-lang/miri#3083 but I can't figure out the point of that name even after looking at the PR.^^ There should be a comment in the benchmark explaining what it is testing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants