Hi, I have used it several times, in a single thread group and I always assumed (and validated) that it represents a fixed % of all requests, from all threads (per user wasn't set). I.e.: the samplers under this controller represented 2% of all transactions recorder, just like the controller was configured.
However, I haven't got the chance to use it since version 2.9 or 2.10, I think, as Constant throughput timer suits my test cases better and gives me the chance to make other interesting configuration. In addition, be careful of nesting of such timers/controllers, some bugs were found in the past due to this and it causes problems with understanding/designing the scenario covered by the script. Cheers, Adrian S On Wed, Mar 12, 2014 at 3:48 PM, Shmuel Krakower <shmul...@gmail.com> wrote: > Hi > > I am using the Throughput Controller across several thread groups which > build up my load test scenario. > I'm having a strange issue where I believe is caused by the fact that the > throughput controller is sharing the calculation across all thread groups > if the "Per User" is not marked and I use the "percent executions". > > As it is not clear from the documentation, my question is what is the > designed sharing mode of the Throughput Controller if the "Per User" is not > set and calculation based on Percent Executions? Is it shared across all > threads in the specific thread group or across all threads across all > thread groups? > > Best, > > Shmuel Krakower. > www.Beatsoo.org - re-use your jmeter scripts for application performance > monitoring from worldwide locations for free. >
