~/utility/load-tester

Global API Load Tester — 10K+ RPS Stress Test

High-performance load testing tool simulating 10,000+ requests per second with geo-distributed traffic, weighted targets, and interactive HTML reports.

testing >99% success GoVegeta Global
proooxy/load-tester — spec
categoryutility / testing
languageGo
stackGo, Vegeta
marketsGlobal
success>99%
outputclean, RAG-ready JSON

key features

Extreme performance — 10,000+ requests per second

Geo-distributed testing from US, EU, and Asia

Weighted multi-target attacks (e.g., 90% reads / 10% writes)

Residential proxy support for realistic traffic

Constant-rate pacing to prevent Coordinated Omission

Interactive HTML reports via Vegeta Plots

Detailed latency, throughput, and error metrics

use cases

  • API performance benchmarking before launch
  • Capacity planning and infrastructure sizing
  • Finding breaking points and bottlenecks
  • Testing CDN and load balancer configurations
  • Geo-distributed latency testing
  • Regression testing for performance-critical endpoints

input parameters

ParameterTypeRequiredDescription
targetsarrayrequiredTarget endpoints with URL, method, body, headers, and weight
ratenumberoptionalRequests per second (default: 50)
durationnumberoptionalTest duration in seconds (default: 60)
geoDistributionarrayoptionalRegions with country codes and traffic weights
useStickySessionsbooleanoptionalMaintain session affinity (default: true)
maxCostLimitnumberoptionalCost ceiling for the test run

Output Example

The load tester generates interactive HTML reports and structured metrics:

 1{
 2  "summary": {
 3    "totalRequests": 50000,
 4    "duration": "60s",
 5    "rps": 833.33,
 6    "successRate": 99.8,
 7    "latency": {
 8      "mean": "12.4ms",
 9      "p50": "10.1ms",
10      "p95": "28.7ms",
11      "p99": "89.2ms",
12      "max": "342.1ms"
13    },
14    "statusCodes": {
15      "200": 49900,
16      "503": 100
17    }
18  }
19}

faq

How does geo-distributed testing work?
You specify country codes and traffic weights. The tool distributes requests across Apify proxy servers in those regions, simulating realistic global traffic patterns.
What is Coordinated Omission?
It's a common load testing pitfall where the tool slows down when the target is overloaded, making results look better than reality. Vegeta uses constant-rate pacing to avoid this.
Can I test authenticated endpoints?
Yes, include authorization headers in the target configuration. Each target can have its own headers, method, and body.

related in ~/utility

Run Global API Load Tester — 10K+ RPS Stress Test, or get a custom build

Start extracting on Apify in minutes, or hire me to build a bespoke scraper and RAG pipeline for your exact source and schema.

run on Apify get custom data