vitessio/arewefastyet

Automated Benchmarking System for Vitess

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

vitessio/arewefastyet has 80+ stars and 50+ forks on GitHub, is written in Go, and was last pushed on Jul 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 19 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 2nd, 2020
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 54
Total Stargazers: 81 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 679.5 days
Mean response time: 453.2 days
90th percentile: 679.7 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 741 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • LFX 2024 Term 2 (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Arewefastyet is an automated benchmarking system that continuously monitors the performance of the Vitess codebase across pull requests and releases.

The tool addresses the need to detect performance regressions as the Vitess codebase evolves. It runs benchmarks using multiple workloads and compares results against the main branch, release branches, recent git tags, and custom git commits. Developers can request benchmarking of a specific pull request by applying a label, triggering automated performance testing that compares the pull request's head commit against its base branch.

The system is designed for teams maintaining Vitess who need systematic performance tracking integrated into their development workflow. It suits projects where performance stability is critical and where pull request-level performance visibility is valuable before merging. The tool runs via Docker and Docker Compose, making deployment straightforward across different environments, though accessing the full system requires secrets for database and benchmarking server connectivity that maintainers must provision.

The project maintains active development with regular updates to its benchmarking infrastructure and measurement capabilities. The codebase shows ongoing refinement of how performance data is collected and compared across different Vitess versions and configurations. Work continues on expanding the range of workloads tested and improving the accuracy of performance comparisons.