Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Continuous performance tracking to avoid major regressions

Open
  • Is something wrong?
#5,103 3 comments 4 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@rami3l is already working on this.

Since Sep 24, 2026.

Assessment

This issue has not been assessed yet.

Description

meta

So far the only ways we use to track performance are:

  • Coarse-grained: running hyperfine.
  • Fine-grained: building with otel and looking at the timeline view.

I think the first part can be automated in some ways: when reading @blyxyas' https://blog.goose.love/posts/making-a-clippy-lint-faster-by-3133x I realized that it may be helpful to keep tracking certain aspects of our runtime performance.

The most important one to track at the moment would be:

  • #2626
Dominant language
Rust
Stars
7k
Forks
1.1k
Avg merge
1d 6h
Merged PRs (30d)
49

Getting set up

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.

More from rust-lang/rustup

All issues in rust-lang/rustup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.