Scalable cloud load/stress testing pipeline solution with Apache JMeter and Terraform to dynamically provision and destroy the required infrastructure on Azure.
When I set up a cluster with below, my JMeter Master CPU utilization is 3.77 GB which is above 90% of the available resource. I cant create a master with more CPU since 4 GB is the maximum allowed CPU. I have the cluster created in West Europe Azure region. Moreover, Neither JMeter Artefacts are generated nor Pipeline run results. So, I dont have any detailed logs to analyse exactly what caused the failure
My load profile: 800 Concurrent Threads with 200 seconds ramp up time and 300 seconds run duration
Master: 4 CPU, 16 GB Memory;
4 Slaves each with 4 vCPU, 16 GB Memory
When I set up a cluster with below, my JMeter Master CPU utilization is 3.77 GB which is above 90% of the available resource. I cant create a master with more CPU since 4 GB is the maximum allowed CPU. I have the cluster created in West Europe Azure region. Moreover, Neither JMeter Artefacts are generated nor Pipeline run results. So, I dont have any detailed logs to analyse exactly what caused the failure
My load profile: 800 Concurrent Threads with 200 seconds ramp up time and 300 seconds run duration Master: 4 CPU, 16 GB Memory; 4 Slaves each with 4 vCPU, 16 GB Memory