codesenberg/bombardier

Fast cross-platform HTTP benchmarking tool written in Go

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 9th, 2026
Created on May 29th, 2016
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 330
Total Stargazers: 6,834 (+0)
Total Subscribers: 88 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 57.9 days
Mean response time: 118.5 days
90th percentile: 355.7 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 594 days
Stale 30+ days: 9
Stale 90+ days: 8

Recent activity

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

Top labels

  • bug (2)
  • feature-request (2)
  • awaiting-feedback (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Bombardier is a HTTP benchmarking tool written in Go that measures the performance of web services under load.

The tool addresses the need for fast, reliable HTTP load testing by leveraging the fasthttp library instead of Go's standard http package, which provides significantly faster performance for benchmarking workloads. It sends concurrent requests to a target server and collects metrics on response times, throughput, and latency distribution. The tool supports both HTTP/1.1 and HTTP/2 testing, with fasthttp as the default high-performance backend and an optional net/http client for RFC compliance or HTTP/2 testing when needed.

Bombardier suits developers and operators who need quick performance validation of web services on their local machines or in CI pipelines. It works across Linux, macOS, and Windows, making it accessible regardless of development environment. The tool is particularly valuable for teams already working in Go who want a lightweight, self-contained benchmarking solution without external dependencies. A known limitation exists around Host header handling with fasthttp; users requiring precise Host header control should use the net/http backend via command-line flags.

The project maintains active build status checks and receives regular updates to support newer Go versions and HTTP standards. Development activity shows responsiveness to compatibility requirements, as evidenced by the addition of HTTP/2 support alongside the original fasthttp implementation. The codebase remains focused on its core benchmarking purpose without scope creep into unrelated features.