rust-lang/rust-analyzer

Consider expanding the benchmark suite

Open

#7,950 opened on Mar 9, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (14,924 stars) (1,726 forks)batch import
A-infraC-enhancementE-mediumS-actionablegood first issue

Description

Once we get in a relatively stable state we should maybe add some more benchmarks. See the discussion in https://github.com/rust-analyzer/rust-analyzer/issues/4186#issuecomment-794236490.

CC @weiznich

Contributor guide

Tech stack
rust
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic Rust knowledgeUnderstanding of benchmark frameworks (e.g., criterion)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Review the linked discussion (https://github.com/rust analyzer/rust analyzer/issues/4186#issuecomment 794236490) to understand which parts of rust analyzer need benchmarking. Examine the existing benchmark suite in the benches/ directory to identify patterns and missing coverage. Propose new benchmarks for critical or unstable code paths, focusing on areas that have changed since the initial benchmark setup.