Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Performance Testing

  • 546 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

performance-testing is a load-testing skill that helps developers design and execute benchmarks measuring response times, throughput, latency, and resource utilization with tools like JMeter and k6 before shipping.

About

performance-testing from aj-geddes/useful-ai-prompts guides developers through designing and running performance tests that measure how systems behave under load. The skill covers response times, throughput, resource utilization, and scalability analysis to find bottlenecks and validate SLAs before release. Triggers include performance test, load test, JMeter, k6, benchmark, latency testing, and scalability analysis requests. It structures quick starts, reference guides, and best practices rather than replacing your observability stack. Developers reach for performance-testing when APIs or services need evidence they meet latency and capacity targets, not just passing functional tests. Pair it with frontend vitals skills when both browser and backend saturation must be validated.

  • Designs and executes k6, JMeter, and custom benchmark scripts
  • Measures response times, throughput, latency, and resource utilization
  • Identifies bottlenecks and validates scalability under load
  • Compares algorithm or implementation efficiency before and after changes
  • Validates caching, database queries, and concurrent user capacity

Performance Testing by the numbers

  • 546 all-time installs (skills.sh)
  • Ranked #608 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill performance-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs546
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you load test APIs before production?

Design and run load tests that measure response times, throughput, latency, and resource usage before shipping.

Who is it for?

Backend and full-stack developers validating SLA targets with JMeter, k6, or similar tools before a production release.

Skip if: Frontend-only teams optimizing Lighthouse Core Web Vitals without server load or scalability testing requirements.

When should I use this skill?

User asks for performance test, load test, JMeter, k6, benchmark, latency testing, or scalability analysis.

What you get

Load test plans, benchmark scripts, throughput and latency reports, and bottleneck findings with resource utilization metrics.

  • Load test scripts
  • Latency and throughput reports
  • Bottleneck analysis

Files

SKILL.mdMarkdownGitHub ↗

Performance Testing

Table of Contents

Overview

Performance testing measures how systems behave under various load conditions, including response times, throughput, resource utilization, and scalability. It helps identify bottlenecks, validate performance requirements, and ensure systems can handle expected loads.

When to Use

  • Validating response time requirements
  • Measuring API throughput and latency
  • Testing database query performance
  • Identifying performance bottlenecks
  • Comparing algorithm efficiency
  • Benchmarking before/after optimizations
  • Validating caching effectiveness
  • Testing concurrent user capacity

Quick Start

Minimal working example:

// load-test.js
import http from "k6/http";
import { check, sleep } from "k6";
import { Rate, Trend } from "k6/metrics";

// Custom metrics
const errorRate = new Rate("errors");
const orderDuration = new Trend("order_duration");

// Test configuration
export const options = {
  stages: [
    { duration: "2m", target: 10 }, // Ramp up to 10 users
    { duration: "5m", target: 10 }, // Stay at 10 users
    { duration: "2m", target: 50 }, // Ramp up to 50 users
    { duration: "5m", target: 50 }, // Stay at 50 users
    { duration: "2m", target: 0 }, // Ramp down to 0
  ],
  thresholds: {
    http_req_duration: ["p(95)<500"], // 95% of requests under 500ms
    http_req_failed: ["rate<0.01"], // Error rate under 1%
    errors: ["rate<0.1"], // Custom error rate under 10%
  },
};

// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
k6 for API Load Testingk6 for API Load Testing
Apache JMeterApache JMeter
pytest-benchmark for Pythonpytest-benchmark for Python
JMH for Java BenchmarkingJMH for Java Benchmarking
Database Query PerformanceDatabase Query Performance
Real-Time MonitoringReal-Time Monitoring

Best Practices

✅ DO

  • Define clear performance requirements (SLAs)
  • Test with realistic data volumes
  • Monitor resource utilization
  • Test caching effectiveness
  • Use percentiles (P95, P99) over averages
  • Warm up before measuring
  • Run tests in production-like environment
  • Identify and fix N+1 query problems

❌ DON'T

  • Test only with small datasets
  • Ignore memory leaks
  • Test in unrealistic environments
  • Focus only on average response times
  • Skip database indexing analysis
  • Test only happy paths
  • Ignore network latency
  • Compare without statistical significance

Related skills

How it compares

Use for server load and SLA proof; use frontend performance skills when the bottleneck is rendering, not request saturation.

FAQ

Which tools does performance-testing cover?

The performance-testing skill explicitly references JMeter and k6 for load tests, benchmarks, and latency analysis. It helps design tests measuring response times, throughput, and resource utilization.

When should developers use performance-testing?

performance-testing applies before shipping when teams must validate scalability, find bottlenecks, and prove latency or throughput requirements under realistic load conditions.

Testing & QAtestingbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.