Yes, does answer my question, thanks Vlad. I am noticing that when the threads are spawned to achieve the target rate, they are closed at the end of the iteration, e.g., the OMTG component starts thread #1, #2, then finishes #1 & #2, then spawns #3, #4 etc. This can be an issue when the threads need to keep context variables to stay in sync with the app under test. For instance, thread #1 starts with a default setting and then will update the setting upon response from the App. But then, when thread #2 comes along, it will start with the default setting again and will be out of sync with the server (unless we reset the app), causing failure. Is there a way to keep the threads that are spawned running until the end of the test instead of starting-closing threads each time?
Robert Bourgault du Coudray Senior QA Engineer | Bankwest Technology Level 4D Bankwest Place 300 Murray Street Perth WA 6000 (08) 9369 9487 | 0468 770 721 robert.bourgaultducoud...@bankwest.com.au bankwest.com.au Bankwest acknowledges the Traditional Owners of the lands across Australia as the continuing custodians of Country and Culture. We pay our respect to First Nations peoples and their Elders, past and present. -----Original Message----- From: Vladimir Sitnikov <sitnikov.vladi...@gmail.com> Sent: Thursday, February 22, 2024 6:17 PM To: JMeter Users List <user@jmeter.apache.org> Subject: Re: Open Model Thread Group questions > Regarding the "Open Model Thread Group" component that was introduced > in version 5.5, can you please explain how this component spins up > threads in order to meet the rate requirements? It launches threads according to the schedule. Each thread executes its body only once. > In particular, how does it handle scripts with multiple HTTP requests > in one iteration: does it check the rate of each request or does it > take the TOTAL number of requests that were sent in that iteration? OMTG does not peek at its contents. It spawns threads with the configured rate, and that is it. If you have several HTTP requests in sequence, they will execute in sequence. For instance, if you configure rate(1/sec) and add 2 HTTP requests without pauses, then each HTTP request will fire with 1/sec rate. Does that answer your question? Vladimir ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ _______________________________________________________________________________ This email has been scanned by the Bankwest Email Security System. _______________________________________________________________________________ _______________________________________________________________________________ Unencrypted electronic mail is not secure and may not be authentic. If you have any doubts as to the contents please telephone to confirm. This electronic transmission including any attachments is intended only for those to whom it is addressed. It may contain copyright material or information that is confidential, privileged or exempt from disclosure by law. Any claim to privilege is not waived or lost by reason of mistaken transmission of this information. If you are not the intended recipient you must not distribute or copy this transmission and should please notify the sender. Your costs for doing this will be reimbursed by the sender. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. _______________________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
