-
Notifications
You must be signed in to change notification settings - Fork 349
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto merge of #3638 - saethlin:big-alloc-bench, r=RalfJung
Add a benchmark for creating large uninit allocations Extracted from #3637 I used this program to confirm that rust-lang/rust#125633 has the desired effect.
- Loading branch information
Showing
3 changed files
with
28 additions
and
0 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
[package] | ||
name = "big-allocs" | ||
version = "0.1.0" | ||
edition = "2021" | ||
|
||
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html | ||
|
||
[dependencies] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
//! This is a regression test for https://github.com/rust-lang/miri/issues/3637. | ||
//! `Allocation`s are backed by a `Box<[u8]>`, which we create using `alloc_zeroed`, which should | ||
//! make very large allocations cheap. But then we also need to not clone those `Allocation`s, or | ||
//! we end up slow anyway. | ||
|
||
fn main() { | ||
// We can't use too big of an allocation or this code will encounter an allocation failure in | ||
// CI. Since the allocation can't be huge, we need to do a few iterations so that the effect | ||
// we're trying to measure is clearly visible above the interpreter's startup time. | ||
for _ in 0..10 { | ||
drop(Vec::<u8>::with_capacity(512 * 1024 * 1024)); | ||
} | ||
} |