rust-lang / rust-lang/rustc-perf

Collect information about maximum used virtual memory

Open
#300 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
732
Forks
189
Avg merge
10h 52m
Merged PRs (30d)
43

Description

This is especially useful in the context of Windows where overcommit is impossible (i.e. it would in most cases show possible regressions in Windows even if tests are run on Linux). Ideal program would have max-rss and max-vmem close to each other.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing where rustc-perf currently records max-rss and how benchmark results are collected on Windows and Linux. Determine how to measure maximum virtual memory and compare max-vmem with max-rss; done means the metric is collected consistently and exposes regressions on Windows without relying on Linux overcommit.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.