rust-lang / rust-lang/rust-analyzer
Benchmark with different allocators
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
The recent paper about https://github.com/microsoft/mimalloc sounds too good to be true.
It might be a good idea to compare different allocators to see if there are some memory usage wins to have. Better perf would also be helpful, but memory usage is the most important thing
Here's the couple of benchmarks that should be representative (you can use any other large project instead of chalk, for example, rust-analyzer itself):
cargo run --package ra_cli --release -- analysis-bench ../chalk/ --complete ../chalk/chalk-engine/src/logic.rs:94:0
cargo run --package ra_cli --release -- analysis-stats ../chalk
I think /usr/bin/time could be used to compare both time and memory (rss)?
We need to compare at least:
- jemalloc
- mimalloc
- system allocator (bonus points if you check with different OSes)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two listed cargo commands for chalk, using /usr/bin/time to capture time and RSS. Investigate how ra_cli and its release build select the allocator, then repeat the benchmarks with jemalloc, mimalloc, and the system allocator. Done means a comparable report of memory usage and performance, with OS differences included if tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100