With NeoLoad you can improve transaction thruput volume, and accurately predict points of failure due to volume
Overall Satisfaction with NeoLoad
Developers use NeoLoad to identify points of failure or potential bottlenecks when placing their transactions under heavy load. Developers using NeoLoad were able to identify bottlenecks and fix/change the code, SQL, increase CPU/Memory, File Handles, Cluster VM's etc, that would not have been apparent under normal testing conditions BEFORE experiencing problems in Production. Also with Production code, we identified the true cause of unknown production slowness.
Pros
- Ability to segment a 'Type' of users in a mix of users.
- Ability to throttle transaction volume at increasing rates while identifying crucial throughput/failure points.
- Ability to test changes like switching to a different Database with precise throughput transaction metrics.
Cons
- Building Test Plans takes time. When the input fields of page changes it breaks the previous plan. The tool would be better if it had a way to migrate an existing plan and adapt to small changes.
- Documentation is fair, but would be improved with more detailed screenshot by screenshot configuration changes rather than summation using words.
- Using NeoLoad Prevented multiple production outages. ROI depends on the criticality of uptime and SLA for a given application.
- It takes Developers time to construct an accurate load test plan.
- Preventing problems is almost always a positive ROI. NeoLoad has indeed benefited our organization compared to its cost.
NeoLoad's ability to provide accurate visual test results in GUI saves developer time. NeoLoad's focus on Load Testing saves developer time when compared to combing thru details of 3 or 4 other products we evaluated. NeoLoad's ability to view live testing metrics/results visually saves developer time and improves the accuracy of identified matters to be addressed.
Comments
Please log in to join the conversation