explaingit

denji/awesome-http-benchmark

3,753Audience · developerComplexity · 1/5Setup · easy

TLDR

A curated list of tools for load testing and benchmarking web servers and APIs, covering everything from simple command-line tools like Apache Bench to scripted frameworks like k6 and Gatling that produce detailed performance reports.

Mindmap

mindmap
  root((HTTP Benchmarks))
    What It Is
      Curated tool list
      Performance testing
      Alphabetical reference
    Tool Types
      Simple CLI tools
      Scripted frameworks
      REST API testers
      Security edge-case tools
    Notable Tools
      Apache Bench
      k6
      Gatling
      Locust
    Use Cases
      Load testing
      CI performance gates
      Security testing
    Audience
      Developers
      DevOps engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Find the right load testing tool for a web service by browsing the categorized list of options sorted alphabetically.

USE CASE 2

Pick a scripting-capable framework like k6 or Gatling for running automated performance tests in a CI/CD pipeline.

USE CASE 3

Locate tools for simulating slow or malformed HTTP connections to check how a server handles misbehaving clients.

USE CASE 4

Use Locust to write complex user behavior scenarios in Python when repeating the same request is not enough.

Getting it running

Difficulty · easy Time to first run · 5min
License terms are not stated in the explanation, check the repository directly.

In plain English

This repository is a curated list of tools for testing how fast a web server or API responds under load. If you have built a website or a web service and want to know how many requests per second it can handle, or how it behaves when many users hit it simultaneously, the tools collected here are what engineers reach for. The list is organized alphabetically and covers a wide range of options. Some tools, like Apache Bench (ab), have been around for decades and are simple to run from a terminal. Others, like Gatling and k6, offer scripting support and produce detailed reports, which suits teams running automated performance tests as part of a build pipeline. A few entries, like Locust, let you describe user behavior in Python code, which is useful when the test scenario is more complex than just sending the same request repeatedly. The list also includes tools for REST API testing and debugging beyond raw load generation, as well as tools for simulating slow or malformed HTTP connections, which is relevant for security testing and checking how servers handle poorly-behaved clients. Most tools listed are open source and run on the command line. The README notes the programming language each tool is written in, which matters if you want to contribute to or inspect the source code, but does not affect how you use them. This is a reference list rather than a tutorial. It points you to each tool's project page so you can evaluate options and choose what fits your stack and testing goals.

Copy-paste prompts

Prompt 1
I want to load test my REST API and need a tool that supports scripted scenarios and exports a detailed report. Which tools in awesome-http-benchmark should I evaluate?
Prompt 2
Compare Apache Bench, wrk, and k6 for load testing a Node.js API, what are the tradeoffs from this list?
Prompt 3
I need to test how my web server handles poorly-formed HTTP requests and slow clients. Which tools in awesome-http-benchmark cover security and edge-case HTTP simulation?
Prompt 4
How do I use Locust to write a load test where users log in, browse a product page, and add to cart, rather than just hammering one endpoint?
Prompt 5
Which tools in this list support running load tests as part of a GitHub Actions CI pipeline with pass/fail thresholds?
Open on GitHub → Explain another repo

← denji on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.