bazel-contrib / bazel-contrib/rules_go

Track and publish performance metrics

Open
#1,609 0 comments 0 reactions 0 assignees View on GitHub
code-health k8s
Dominant language
Go
Stars
1.5k
Forks
760
Avg merge
1d 11h
Merged PRs (30d)
12

Description

* We need a benchmark that measures how long it takes to build various targets. This should include minimal "hello world programs", various popular Go libraries, and significant targets in Kubernetes. It should measure clean builds and incremental (single file change) builds.
* This benchmark should be run regularly and automatically (likely in a cron job somewhere).
* The results should be published somewhere that's publically visible (a public Google Sheet with a pretty graph would be a minimum viable product).

Contributor guide

Open the contributing guide

Research direction

No files, tests, or existing entry points are named. First map how Go targets and Kubernetes targets are built, then determine where clean and single-file incremental benchmarks can run on a schedule and how results can be published publicly; done means recurring measurements and visible results for the requested target groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, ci-cd, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.