Ok I have always use "synchronizing timer"/rendez vous but your solution seem interesting
Antonio 2016-09-21 14:25 GMT+02:00 Vladimir Sitnikov <sitnikov.vladi...@gmail.com>: > Antonio>What do you mean by ""Bursty load" simulation. There is no easy way > to test > Antonio>"50 iterations per hour as 10 bursts of 5 items"? > > There are two cases there: > 1) The main problem is how would you create a load when two actions are > very close "by pure chance"? > For instance, current CTT will eventually create very even distribution > with all pauses equal (assuming > the response times are stable). > By default, if you launch "360 per hour", you might expect "one sample > every 10 seconds": 0, 10, 20, 30, ... > > That would miss cases when "two samples took place at very similar point in > time" like 0, 11, 12, 30, .. > > "Poission process" models that appropriately. Even though it creates > "constant throughput", the particular > arrival times are random, so multiple events can appear close to each > other. > > 2) "Always start 5 samples at once". Something like that can be achieved by > current "synchronizing timer", > however there are cases when you need to "test rare cases that always come > in pairs" > > Vladimir >
