> 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
