Vincent>Usually I do not model the load in urls/sec but in full scenarios
(from
Vincent>login to logout) per hour in high activity.
Ah, it looks like you misunderstand my proposal.
The proposed "Precise Thread Group" measures workload rate in scenarios
rather than "URLs or samplers".
It does not care how many samplers are there in the thread group, and what
it does is it ensures the number of "execution launches"
matches the configured rate.
Vincent>200 new document creations per hour + 400 document searches per
hour + 250
Vincent>document modifications / hour.
Let me put some examples:
1) If you have exact rates for scenarios, then you could configure 3 thread
groups with the required rates.
Note that "document creation scenario" could have an arbitrary number of
samples inside, and the rate is per scenario rather than "per sample".
Precise Thread Group: schedule="rate(200/hour) random_arrivals(30 min)"
- "document creation scenario"
Precise Thread Group: schedule="rate(400/hour) random_arrivals(30 min)"
- "document search scenario"
Precise Thread Group: schedule="rate(250/hour) random_arrivals(30 min)"
- "document modification scenario"
2) On the other hand, if you do not have specific rates, but you want to
have a single "850 scenarios per hour" + percentages,
you could use "throughput controller" or something like that to divide 850
into the three scenarios.
Suppose the breakdown is 200:400:250 == 24% : 47% : 29%, and the total rate
is 200+400+250 == 850 per hour
The test could be:
Precise Thread Group: schedule="rate(850/hour) random_arrivals(30 min)"
- Throughput Controller: probabiltity=24%
- "document creation scenario"
- Throughput Controller: probabiltity=47%
- "document search scenario"
- Throughput Controller: probabiltity=29%
- "document modification scenario"
Both options would generate the desired "200 + 400 + 250" per hour
workload, and I do not see why would you like to use pacing.
>I prefer to use the concept of pacing which is simpler and which allows
>easily to make load with step (100% load 1h then 150% load 1h)
I do not see why do you think "pacing" makes the test easier. Where does it
help exactly?
You can launch JMeter multiple times with different parameters (that is
what I do because I have a runner for that),
or you could configure Precise Thread Group to do several steps of load
like "rate(850/hour) random_arrivals(30 min) pause(0) rate(1700/hour)
random_arrivals(30 min)"
Vladimir
