Open jonatanvicente opened 8 months ago
ItaChallenge JMeter report - 100-10.csv ItaChallenge JMeter report - 1000-10.csv ItaChallenge JMeter report - 2000-10.csv ItaChallenge JMeter report - 3500-10.csv ItaChallenge JMeter report - 3500-100.csv ItaChallenge JMeter report - 4000-10.csv ItaChallenge JMeter report - 5000-10.csv ItaChallenge JMeter report - 5000-100.csv ItaChallenge JMeter report - 6000-100.csv ItaChallenge JMeter report - 6500-100.csv ItaChallenge JMeter report - 7000-100.csv
Es necesario ejecutar pruebas de carga sobre el microservicio Challenge que está desplegado en DEV, atacando http://87.106.229.175:9080/itachallenge/api/v1/challenge/challenges
MUY IMPORTANTE: Las pruebas de carga pueden hacer caer la plataforma DEV. ES NECESARIO AVISAR ANTES DE EJECUTAR LOS PASOS SIGUIENTES
Efectuar los siguientes pasos (en ese orden):
Some more explanations :)....
Load ramping As a general guideline, you might start with a small number of concurrent users (e.g., 10 or 100, depending on the expected load), and gradually increase the load while monitoring the performance and resource usage of your application. This process, known as load ramping, can help you identify the maximum number of concurrent users your application can handle before performance degrades unacceptably. In load ramping, it's generally better to start with a few concurrent users and gradually increase the load over a longer period of time. This approach allows you to observe how your system behaves under increasing load and identify any potential bottlenecks or performance issues.
Spike testing (stress) Starting with many concurrent users in a short time, also known as a spike test, can also be useful, but it's more of a stress test designed to see how your system handles sudden, extreme increases in load. This can be useful for identifying issues that only appear under high load, but it doesn't give you as much information about how your system behaves under more typical conditions.
In general, a combination of both approaches can be beneficial. Start with load ramping to observe the system behavior under normal and increasing load, then perform spike tests to see how it handles sudden, high load. This will give you a more complete picture of your system's performance characteristics.