Scribd
Upload
25 views2 pages

Load Testing Report Client

The load testing for the Charttwits Mobile Application evaluated performance with 1500 concurrent users using Apache JMeter across various ramp-up periods. Key findings indicated acceptable response times at 900s ramp-up, while 30s ramp-up showed spikes and failures. Overall, the application performed well, particularly with 300s and 900s ramp-up, suggesting further optimization is needed for shorter ramp-ups.

Uploaded by

thirupathi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views2 pages

Load Testing Report Client

The load testing for the Charttwits Mobile Application evaluated performance with 1500 concurrent users using Apache JMeter across various ramp-up periods. Key findings indicated acceptable response times at 900s ramp-up, while 30s ramp-up showed spikes and failures. Overall, the application performed well, particularly with 300s and 900s ramp-up, suggesting further optimization is needed for shorter ramp-ups.

Uploaded by

thirupathi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Load Testing Summary Report

Project: Charttwits Mobile Application Load Testing

Date: 05-26-2025

Tool Used: Apache JMeter

Test Conducted By: Mechknow Soft LLC

Objective
To evaluate the performance and stability of the web application under a simulated load of
1500 concurrent users using different ramp-up periods: 30s, 150s, 300s, and 900s.

Test Setup
Users 1500
Loop Count 1
Ramp-Up Periods 30s, 150s, 300s, 900s
Total Requests POST & REPOST APIs
Environment AWS Hosted Server
Tool Apache JMeter

Scenarios Tested
Scenario Ramp-Up Time Purpose
Test 1 30 seconds High burst load test to
simulate sudden traffic
Test 2 150 seconds Moderate ramp-up to
observe API behavior under
pressure
Test 3 300 seconds Balanced ramp-up for
stability analysis
Test 4 900 seconds Gradual load test to
simulate organic traffic
increase

Key Observations
 ✅ All APIs responded under acceptable response time thresholds for 900s ramp-up.
 ⚠️At 30s ramp-up, response time spikes and some failures were observed due to
sudden load.
 📉 Gradual ramp-up helped maintain high success rate and lower response time.
 🚀 POST and REPOST APIs were the primary focus of the test.

Attached Summary Reports


 📄 1500 Users with 30s Ramp-Up (CSV)
 📄 1500 Users with 150s Ramp-Up (CSV)
 📄 1500 Users with 300s Ramp-Up (CSV)
 📄 1500 Users with 900s Ramp-Up (CSV)

Conclusion
The application successfully handled up to 1500 concurrent users with varying ramp-up
periods. Optimal performance was observed with 300s and 900s ramp-up. Further fine-
tuning of server resources and response handling could help improve short ramp-up
scenarios (e.g., 30s).

You might also like