How to Perform Apache JMeter Non GUI Mode Distributed LoadTesting or Remote LoadTesting

preview_player
Показать описание
How to Perform Apache JMeter Non GUI Mode Distributed LoadTesting or Remote LoadTesting
Рекомендации по теме
Комментарии
Автор

Hi Sir, Nice video I really appreciate the efforts and time that you have put into this video.

Need your help on my case.
I have added 16 Concurrency thread groups in my test plan. When running with 2K users with distributed load across 19 slave servers, I can see the summary report on the command prompt when running the command " tail -f -n 2 MVP_2K_Run.log ".
But when running the same test plan with 15K thread (users) across the 19 slave server and running the same tail command then stuck at "Waiting for possible message on port 4445" and there is no summary showing on the command prompt but the log and Jtl file is getting generated.

I have run my test plan with 15K users and distributed the load on 19 servers using the below command

nohup -n -t MVP5.2_BaseLinePT_15K.jmx -l -R <<1 to 19 slave servers ip address> :4000 > 2>&1 &

JTL and log files are created on the master server under the specified path but a summary of execution like the number of threads started, active, and finished and error rate percentage are not showing on the command prompt when running the below command tail command (tail -f -n 2

It shows the below details only.

Remote engines have been started:[1 to 19 slaver server IP details] Waiting for possible message on port 4445

I divided the total number of threads by 19 and then added it to the concurrency thread group.

For example, if I have to test one scenario with 2000 VU, then 2000/19 = 105. So I am passing 105 Vu in the 1st currency thread group for 1 hour.
1500 VU in the second scenario, then 1500/19 = 79, so we added 79 VU in the second concurrency thread group for 1 hour.

Like this, I have added it to the 16-concurrency thread group for 1 hour.

Please help me to solve these problems.

Also, the generated JTL file is getting very heavy for 60K VU (approximately 4.5 GB in size) please help me to reduce the size of the JTL file.

thedubaiworld