Skip to content
Skills Library
DevOps & cloud · Testing

load-testing

/load-testing

Simulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Simulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.

Original author description

Simulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.

How it works

  1. Method
  2. Signals
  3. Boundaries
Original SKILL.md headings · 55 lines, 458 words
SKILL.md preview
---
name: load-testing
description: Simulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.
---

# Load testing

A load test that fires requests as fast as a loop allows measures your load
generator, not your users. Real traffic arrives in waves, with pauses between
actions and a mix of endpoints, from clients spread across a network. Model
that shape honestly or you will size the system for a workload that never
happens and be surprised by the one that does.

## Method

1. **Model the scenario from real traffic.** Pull endpoint mix, request
   ratios, and payload sizes from production logs or access metrics. A test
   that hammers one cheap endpoint proves nothing about a homepage that fans
   out to eight services.
2. **Add think time between steps.** Insert realistic pauses, one to several
   seconds, between a user's actions. Zero think time concentrates load into
   an unnatural burst and inflates contention that real users never create.
   In k6, Locust, or Gatling this is an explicit sleep or pace setting.
3. **Ramp, do not slam.** Start at low concurrency and increase virtual users
   in stages, holding each level long enough to reach steady state. A step
   ramp shows how latency responds to load; a cold jump to full concurrency
   only shows connection-storm behavior.
4. **Run the generator off the system under test.** Drive load from separate
   machines close in the network to the target. A generator sharing CPU with
   the service competes with it and corrupts every number you collect.
5. **Watch for the saturation knee.** As you add users, throughput rises then
   flattens while latency climbs: that inflection is the capacity limit.
   Report the concurrency at the knee, not the maximum requests you managed
   to push through it.
6. **Assert on percentiles and error rate, not the mean.** Gate on p95 and
   p99 latency and the failure rate against the service level objective. An
   average of 80ms can hide a p99 of four seconds and a rising stream of 500s.
7. **Push to failure once, on purpose.** In an isolated environment, ramp
   past the knee until the system breaks and record how: queue overflow,
   timeouts, out-of-memory. Knowing the ceiling and the failure mode is worth
   more than a clean pass.

## Signals

- Does the load profile reproduce production's endpoint mix and pacing, or
  just one hot loop?
- Can you name the concurrency level where latency crossed the objective and
  the mode the system failed in beyond it?
- Are your reported numbers percentiles under sustained steady-state load,
  not averages from the ramp?

## Boundaries

Load testing sizes a system under concurrent traffic; single-function timing
belongs to performance-testing. It measures behavior under load, not behavior
under failure: deliberately killing instances or injecting latency is
chaos-testing. Capacity targets and cost ceilings are product and budget
decisions this test informs but does not set.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
claude-dev-suite/claude-dev-suite100MIT
SkillMedev/skills100MIT
ajyadav013/claude-kit100MIT
ajyadav013/claude-kit100MIT
rnavarych/alpha-engineer100MIT
VilnaCRM-Org/rust-service-template96CC0-1.0
OKHP3/skillz90MIT
arjunprabhulal/devops-skills90MIT

Database snapshot: 13.11.2026 · package version 61a3803749ba (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100load-test
    Load testing setup, execution, and analysis with k6, Artillery, or Locust. Generates test scripts, defines VU ramp-up scenarios, interprets p99 latency and error rate results, and suggests infrastructure fixes. Use when user wants to load test an API, check throughput limits,…
  • 100scaling-review
    Read-only scaling review that finds what breaks first at 10x and 100x load across app code, queues, caches, databases and infra (AWS, GCP, Azure, Railway, Cloudflare, VPS/Docker) and ends in a ranked findings report. Use for "will this scale", "what breaks at 10x traffic", "what…
  • 100locust-load-test
    Load test any project's API or web service with Python, locust and uv. Scans the code base for every endpoint, sorts them into core, support and peripheral features, asks the user which test level to run for each (smoke, expected load, stress) and which user-load scenario to…
  • 90capacity-planning
    Ensures a system has enough headroom before it needs it, by forecasting growth, modeling load against real saturation signals, and accounting for the lead time it takes to actually add capacity. Use this whenever the user asks whether current infrastructure can handle projected…
  • 100ai-stress-test
    Test system behavior under extreme load to find breaking points, capacity limits, and failure modes. Covers stress, spike, and breakpoint testing with k6 (primary), JMeter, or Locust. Refuses unbounded concurrency and production saturation without explicit approval. Trigger for…
  • 100load-testing-methodology-stress-soak-spike
    Use this skill when executing stress, soak, and spike load tests to determine system capacity boundaries and graceful degradation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.