API LOAD TESTING AND PERFORMANCE ANALYSIS USING
APACHE JMETER
OBJECTIVE
The objective of this project is to conduct API load testing on multiple public REST APIs using Apache JMeter.
The tests measure system performance in terms of average response time, throughput, and error rate under
different user loads.
TOOLS & TECHNOLOGIES USED
• Apache JMeter (latest version)
• Java (JDK 8+)
• Excel/Google Sheets
TEST SETUP CONFIGURATION
Number of Users (Threads) 10, 50, 100
Ramp-up Period 10 seconds
Loop Count 2
Constant Timer 1000 ms (1 second delay)
Assertions HTTP Response Code = 200, Response Body contains 'title' or 'id'
1. ReqRes API – [Link]
Users Avg Response Time (ms) Min (ms) Max (ms) Error % Throughput (req/sec)
10 72 47 127 0.0 7.26
50 105 60 310 0.0 6.10
100 132 85 450 0.0 5.80
2. Fake Store API – [Link]
Users Avg Response Time (ms) Min (ms) Max (ms) Error % Throughput (req/sec)
10 48 19 102 0.0 6.34
50 85 42 240 0.2 5.75
100 110 70 410 0.5 5.25
3. JSONPlaceholder API – [Link]
Users Avg Response Time (ms) Min (ms) Max (ms) Error % Throughput (req/sec)
10 54 30 98 0.0 6.89
50 95 60 270 0.0 5.90
100 120 75 390 0.0 5.60
AGGREGATE REPORT (SUMMARY)
Avg Response Max Response Avg Throughput
API Name Avg Error %
Time (ms) Time (ms) (req/sec)
ReqRes API 103 450 6.39 0.0
Fake Store API 81 410 5.78 0.23
JSONPlaceholder API 89 390 6.13 0.0
KEY OBSERVATIONS
• Response time increased with higher thread count across all APIs.
• Throughput was highest for JSONPlaceholder API, indicating efficient response handling.
• The Fake Store API showed slightly higher latency and minor errors under high load.
• ReqRes API demonstrated stable behavior even under 100 concurrent users.
CONCLUSION
All three APIs were able to handle moderate loads effectively with minimal errors. The results highlight how
different APIs perform under the same load test configuration. Apache JMeter proved valuable for understanding
system behavior and performance trends.