uber/h3

Collect and monitor benchmark performance

Open

#530 opened on Oct 30, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C (585 forks)github user discovery
help wanted

Repository metrics

Stars
 (6,310 stars)
PR merge metrics
 (Avg merge 7d 19h) (17 merged PRs in 30d)

Description

Contributor guide

Research direction
Evaluate existing GitHub Actions for continuous benchmarking and design a workflow to run H3 benchmarks on each PR, storing results for comparison.
Tech stack
c
Domain
ci cdperformance
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
CGitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30