Design and execute performance tests to measure response times, throughput, and resource utilization. Use for performance test, load test, JMeter, k6, benchmark, latency testing, and scalability analysis.

Performance Testing Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) 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: Reference Guides Detailed implementations in the references/ directory: Guide Contents [k6 for API Load Testing](references/k6 for api load testing.md) k6 for API Load Testing [Apache JMeter](references/apache jmeter.md) Apache JMeter [pytest benchmark for Python](references/pytest benchmark for python.md) pytest benchmark for Python [JMH for Java Benchmarking](references/jmh for java benchmarking.md) JMH for Java Benchmarking [Database Query Performance](references/database query performance.md) Database Query Performance [Real Time Monitoring](references/real time monitoring.md) Real 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

performance-testing