vipergreat commented on issue #5966: URL: https://github.com/apache/jmeter/issues/5966#issuecomment-1630415634
Hi Vlad I have some use case to share. I'm reproducing the production issue by using JMeter and I think the Open Model Thread Group is the answer. Actually we comparing with bzm - Free Form Arrival Thread Group but I think OMTG is easier to config. We has APIs as follows 1. /api/welcome 2. /api/login <--- This API was pain 3. /api/verify-input 4. /api/submit-input <--- we will simulate response time from 1 sec to 30 sec 5. /api/logout We have number of Customer arriving rate from the load balancer. It's around 10k/min (we count only first API - welcome). On that day the API no.4 is slow from 1 seconds to 30-40 seconds. We found API no.2 is pain but another API still fine. So my hypothesis is when Customers wait API no.4 too long they will kill the app and try login and input data again and again the arriving rate increase to 20-25k/min. So the thread lifetime is represent Customer can't wait and kill the app. It's may config the lifetime to only 1-2 minutes per thread. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
