Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for software architects

Performance and Scalability Load Test Agent

Know the system's safe capacity and fix bottlenecks before launch

Performance and Scalability Load Test Agent: what goes in, what the agent does and what you get

What it does

Before a launch or a big change, teams need to know where the system will break, not find out on the day. This agent builds a load model from production traffic patterns, then asks the owner to approve a test time in staging. It runs load tests at rising levels and reads response times, error rates, traces and resource use. A level passes when the 95th percentile response time and error rate stay within targets for the full run. Tests stop if errors pass 5 percent. When a target is missed, it looks for the bottleneck in traces and metrics, proposes a fix and reruns after the fix is applied. It writes a capacity report with the safe level and the first bottleneck. Edge case: if staging is much smaller than production, results are scaled carefully and marked as estimates.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
ApprovedYes, continueNo 1 STARTS WHEN Release or traffic event scheduled 2 DOES Build load model from production traffic 3 YOU APPROVE Owner approves test time in staging 4 USES A TOOL Run load test at rising levels 5 USES A TOOL Read response times, errors, traces and resource use 6 CHECKS THE RESULT Did the target load pass? If not: find the bottleneck, propose a fix, and rerunafter it is applied. Back to step 4. 7 DOES Write capacity report 8 RESULT Capacity report and bottleneck list
Read the steps as a list
  1. Release or traffic event scheduled
  2. Build load model from production traffic
  3. Owner approves test time in stagingThe agent waits here for your OK.
  4. Run load test at rising levels
  5. Read response times, errors, traces and resource use
  6. Did the target load pass?If not: find the bottleneck, propose a fix, and rerun after it is applied. Back to step 4.
  7. Write capacity report
  8. Capacity report and bottleneck list

How it decides

A load level passes when the 95th percentile response time and error rate stay within targets for the full run.

  • Targets use 95th percentile, not averages
  • Results from smaller staging are marked estimates
  • Tests stop when error rate passes 5 percent

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Performance targets
  • Load levels
  • Staging scale factor
  • Error stop limit (default 5 percent)

What keeps you in control

It always asks you first

  • Running tests in shared environments
  • Any production test

Hard limits

  • Never load tests production without explicit approval
  • Stops tests when errors exceed the limit

It stops when

  • Done: target passes
  • Stop: bottleneck needs an architecture change

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensAhead of a November 20 sale, the target was 800 requests per second at 500 ms. The checkout API failed at 600 requests per second, with 95th percentile at 2.4 seconds. Traces showed a slow query on the orders table with no index. The developer added the index and the owner approved a second run. It passed 900 requests per second at 380 ms.

More agents for software architects