api-load-tester

API load testing measures performance under simulated traffic by monitoring latency, error rates, and throughput. This Skill uses Bash commands and tools like hey or wrk to gradually increase concurrency and identify breaking points.

Stress testing a REST API is best done by gradually increasing concurrent requests to find breaking points. This Skill generates detailed reports containing latency percentiles, throughput curves, and bottleneck analysis for performance insights.

Yes, you need dependencies like hey, wrk, ab, or curl installed to run HTTP stress tests. The Skill invokes these tools via Bash commands to execute load tests and requires Read, Write, Glob, and Grep capabilities to generate reports.

You can customize API endpoint testing by specifying target endpoints, acceptable latency thresholds, and concurrency ranges. This allows progressive concurrency testing to accurately identify exactly when and where your API performance degrades.

API throughput drops under increased concurrent load when the system hits a bottleneck. This Skill identifies these breaking points through progressively increasing traffic, generating detailed reports that analyze latency curves and error rates.

Using curl for load testing provides basic HTTP requests but lacks advanced throughput metrics compared to wrk. While curl handles simple endpoint checks, wrk and hey offer superior progressive concurrency and detailed latency percentile reporting.