Skip to content

■ SKILLS // SKILL SPECS

performance-test-suite

Load testing and performance benchmarking with metrics analysis and bottleneck identification

■ [!] ON THIS PAGE ▼
■ INSTALL // npx @self.md/cli install performance-test-suite
AuthorJeremy Longshore
Namespace@jeremylongshore/claude-code-plugins-plus
Category#security
Version1.0.0
Stars★ 1,193
Downloads↓ 2
Verification[ ✓ ] self.md verified

Load testing and performance benchmarking with metrics analysis and bottleneck identification

Installation

npx claude-plugins install @jeremylongshore/claude-code-plugins-plus/performance-test-suite

Contents

Folders: agents, skills

Files: LICENSE, README.md

Documentation

Comprehensive load testing and performance benchmarking with intelligent metrics analysis, bottleneck identification, and actionable recommendations.

Features

  • Load testing - Gradual ramp-up, sustained load, peak capacity
  • Stress testing - Breaking point identification, recovery validation
  • Spike testing - Sudden traffic surges, flash sale scenarios
  • Endurance testing - Long-running stability, memory leak detection
  • Metrics analysis - Response times, throughput, error rates, resources
  • Bottleneck identification - CPU, memory, database, network issues
  • Comprehensive reporting - Percentiles, graphs, recommendations

Installation

/plugin install performance-test-suite@claude-code-plugins-plus

Usage

The performance testing agent activates automatically when discussing performance or load testing:

Design load test

Create a load test for the API that ramps up to 500 concurrent users over 5 minutes

Stress test to find limits

Design a stress test to find the breaking point of the checkout API

Spike test for flash sales

Create a spike test simulating a flash sale with sudden 10x traffic increase

Endurance test for stability

Design an endurance test running at 200 users for 4 hours to check for memory leaks

Test Types

1. Load Testing

Gradually increase load to test normal operating conditions:

// k6 load test
export let options = {
  stages: [
    { duration: '5m', target: 100 },   // Ramp up
    { duration: '10m', target: 100 },  // Sustain
    { duration: '5m', target: 0 },     // Ramp down
  ],
};

Validates:

  • Normal performance under expected load
  • Response times remain acceptable
  • Error rates stay low
  • Resources adequate for traffic

2. Stress Testing

Push system beyond normal load to find limits:

// k6 stress test
export let options = {
  stages: [
    { duration: '2m', target: 100 },
    { duration: '5m', target: 200 },
    { duration: '5m', target: 300 },
    { duration: '5m', target: 400 },
    { duration: '10m', target: 400 },
  ],
};

Validates:

  • Maximum capacity before failure
  • Graceful degradation under stress
  • Recovery after overload
  • Error handling at limits

3. Spike Testing

Sudden dramatic traffic increases:

// k6 spike test
export let options = {
  stages: [
    { duration: '10s', target: 50 },    // Normal load
    { duration: '1m', target: 500 },    // Sudden spike
    { duration: '3m', target: 500 },    // Sustain spike
    { duration: '10s', target: 50 },    // Return to normal
  ],
};

Validates:

  • Auto-scaling response
  • Rate limiting effectiveness
  • System stability during surge
  • Recovery time after spike

4. Endurance Testing (Soak Test)

Extended duration at moderate load:

// k6 endurance test
export let options = {
  stages: [
    { duration: '2m', target: 200 },
    { duration: '4h', target: 200 },    // Long soak
    { duration: '2m', target: 0 },
  ],
};

Validates:

  • Memory leaks over time
  • Resource exhaustion
  • Connection pool issues
  • Long-term stability

Metrics Collected

Response Time Metrics

  • Average - Mean response time
  • Median (P50) - Half of requests faster
  • P95 - 95% of requests faster (SLA metric)
  • P99 - 99% of requests faster (tail latency)
  • Max - Slowest request

Throughput Metrics

  • Requests/second - Total throughput
  • Success rate - Percentage successful
  • Error rate - Percentage failed
  • Data transferred - Bandwidth usage

Resource Metrics

  • CPU usage - Average and peak utilization
  • Memory usage - Allocation and growth
  • Network I/O - Bandwidth consumption
  • Disk I/O - Read/write operations
  • Database connections - Pool usage

Bottleneck Identification

The agent identifies common performance issues:

High CPU Usage

  • Inefficient algorithms
  • Missing caching
  • Excessive computations
  • Unoptimized loops

High Memory Usage

  • Memory leaks
  • Large object retention
  • Inefficient data structures
  • Missing garbage collection

Slow Database

  • N+1 query problems
  • Missing indexes
  • Inefficient queries
  • Connection pool exhaustion

Network Saturation

  • Large response payloads
  • Missing compression
  • Too many requests
  • Inefficient protocols

Example Report

Performance Test Report
=======================
Test: Load Test - API Endpoints
Date: 2025-10-11 14:30:00
Duration: 20 minutes
Max Virtual Users: 300

 Response Time Metrics
  Average: 145ms
  Median (P50): 120ms
  P95: 280ms  (Target: <300ms)
  P99: 450ms  (Target: <500ms)
  Max: 1,230ms

 Throughput
  Total Requests: 90,000
  Requests/sec: 75
  Success Rate: 99.4% 
  Error Rate: 0.6%

 Resource Utilization
  CPU: 68% avg, 87% peak
  Memory: 2.8 GB / 4 GB (70%)
  Network: 22 MB/s avg

 Bottlenecks Identified
  1. GET /api/users - P95: 850ms (database index needed)
  2. Database conn

...(truncated)

## Included Skills

This plugin includes 1 skill definition:

### running-performance-tests

> |

<details>
<summary>View skill definition</summary>

# Performance Test Suite

This skill provides automated assistance for performance test suite tasks.

## Prerequisites

Before using this skill, ensure you have:
- Test environment configured and accessible
- Required testing tools and frameworks installed
- Test data and fixtures prepared
- Appropriate permissions for test execution
- Network connectivity if testing external services

## Instructions

### Step 1: Prepare Test Environment
Set up the testing context:
1. Use Read tool to examine configuration from {baseDir}/config/
2. Validate test prerequisites are met
3. Initialize test framework and load dependencies
4. Configure test parameters and thresholds

### Step 2: Execute Tests
Run the test suite:
1. Use Bash(test:perf-*) to invoke test framework
2. Monitor test execution progress
3. Capture test outputs and metrics
4. Handle test failures and error conditions

### Step 3: Analyze Results
Process test outcomes:
- Identify passed and failed tests
- Calculate success rate and performance metrics
- Detect patterns in failures
- Generate insights for improvement

### Step 4: Generate Report
Document findings in {baseDir}/test-reports/:
- Test execution summary
- Detailed failure analysis
- Performance benchmarks
- Recommendations for fixes

## Output

The skill generates comprehensive test results:

### Test Summary
- Total tests executed
- Pass/fail counts and percentage
- Execution time metrics
- Resource utilization stats

### Detailed Results
Each test includes:
- T

...(truncated)

</details>

## Source

[View on GitHub](https://github.com/jeremylongshore/claude-code-plugins-plus-skills)