Testvox made a structured plan for speed testing to find problems and give the client the confidence to grow.
- A method for testing with gradual loads
We started testing with 500 users and slowly added more until we had 1,000 users and then 2,000 people. When errors showed up when the server had a lot of traffic, we closely watched the server metrics to find the reasons. The production team was told about the findings so that they could be fixed right away.
- Testing Again After Optimisation
After Weblanza made the changes that were suggested, we ran the tests again, this time with up to 5,000 people at the same time. Carefully keeping an eye on the server's performance, more tweaks were made until steadiness was reached with acceptable response times.
- Tough analysis and monitoring
We tested for load, stress, and endurance with JMeter. A lot of attention was paid to how much CPU, memory, and network speed were used. The tests kept going until the CPU usage levelled off below reasonable levels and performance as a whole got a lot better.
- Testing in a production environment
The app was already live, so testing had to be done in the production setting, where real users wouldn't be affected. To deal with this, testing was done when no one was working, so it wouldn't affect people who were bidding at the time.