I have a question that has to do with the Throughput Shaping Timer usage. Maybe I have to use another plugin to cover my demand, but anyway I decided at least to investigate it and understand the behavior.
The task - emulate 20 TPS on the platform for the following user scenario:
But with the strict TPS distribution:
- Login - 1 TPS
- Get user info - 6 TPS
- Search - 12
- Logout - 1 TPS
Throughput Shaping Timer investigation
I made the following:
Added the "Concurrency thread group" with flexible settings, just to be lazy and delegate the threads set up to the plugin.
Results/questios:
- I got 4.8 TPS on average for all requests (I suppose it's expected for the current flow)
- General TPS time to time is more than 20 TPS set in the test. Is it OK, or some settings are incorrect? from my understanding the peaks are too high..
- Some requests have TPS peaks, looks not very good due to peaks
So the questions:
- Is it possible to apply some tunings (or set/change flow) for the current stack of the tools ("Concurrency thread group" with flexible settings and "Throughput shaping timer") to distribute target 20 TPS like described in the task?
- How "Throughput shaping timer" divide the TPS between threads?
- Please suggest the best solution for the current task
Many thanks