google/benchmark

A microbenchmark support library

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 12th, 2013
Open Issues & Pull Requests: 176 (+0)
GitHub issues: Enabled
Number of forks: 1,800
Total Stargazers: 10,389 (+0)
Total Subscribers: 200 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 hours
Mean response time: 83.2 days
90th percentile: 302.8 days
Tracked items: 125

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% of issues opened in the past year have been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 38
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 748 days
Stale 30+ days: 30
Stale 90+ days: 24

Recent activity

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

Top labels

  • help wanted (35)
  • good first issue (16)
  • enhancement (12)
  • os:windows (10)
  • bug (9)
  • docs (5)
  • incomplete (3)
  • os:osx (1)

Detailed Description

Benchmark is a microbenchmark support library for C++ that helps developers measure and analyze the performance of code at fine granularity.

The library addresses the challenge of accurately measuring small code sections where timing precision matters and noise from the measurement process itself can skew results. It provides infrastructure to run code repeatedly, collect timing statistics, and filter out measurement overhead. The approach works by defining benchmark functions that execute a workload multiple times, with the library handling timer management, statistical aggregation, and result reporting across different scenarios.

Developers should choose this tool when they need to verify performance characteristics of critical code paths, compare algorithmic approaches, or track performance regressions over time. It suits projects where micro-level performance matters—systems programming, performance-sensitive libraries, or any codebase where understanding the cost of individual operations is important. The library integrates into C++ projects as a testing dependency and produces human-readable output showing timing statistics for each benchmark.

The project maintains steady activity with regular commits addressing bug fixes and incremental improvements. Development focuses on reliability of measurements and usability of the benchmarking interface rather than feature expansion. The maintainers respond to issues and pull requests, indicating active stewardship of the codebase.