rust-lang / rust-lang/rustc-perf

Perfbot commands for evaluating only size

Open
#1,888 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi, I don't know if this is the appropriate spot to mention this request, please feel free to redirect me if not! For WG-binary-size purposes, it might be nice to have a perfbot command to evaluate a PR strictly for its binary size impact. For a lot of such PRs, it's inappropriate to run the entire perf infrastructure because we don't expect any appreciable cycle or wall time impact, and if we do we'd probably be fine following it up reactively, and we'd rather not take up extra queue time if we don't have to.

This is especially the case with "library-only" PRs which affect fairly fiddly bits of standard library code and touch their code size.

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

Review the existing perfbot command entry points and the WG-binary-size workflow first. Determine how a command can evaluate only a pull request's binary size impact without running the full performance infrastructure. Done means the command performs that focused evaluation and its behavior is covered by the project's relevant checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance, tooling
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.