bazelbuild/bazel

Documentation for performance is fragmented

Open

#11,384 opened on May 13, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-Documentationteam-Performancetype: documentation (cleanup)

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

The documentation about performance is in different places:

I think it would be useful to consolidate the information in one place.

This blog post may also contain information to put in the documentation: https://filipnikolovski.com/posts/bazel-performance-in-a-ci-environment

Contributor guide

Research direction
Consolidate the performance documentation from the three listed URLs and the blog post into a single document under the docs folder.
Tech stack
java
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70