>Why not call it « Open Model thread group » instead of precise throughput >thread group?
Naming is hard, and I have no idea of the proper name. Suggestions are welcome. I used "precise thread group" just to pick a name and get the thing running. I think "open model thread group" is not exactly right since after thread(N) addition the thread group is no longer "open model". On the other hand, a sufficiently large number of threads in "closed model" is not really different from "open model", so the existing thread groups are "open" as well if user configures big enough threat counts. >Precise is a bit weird as it would mean others are not. The thing is the new group generates the accurate load in terms of the number of samples. For instance, if you configure rate(10/min) random_arrivals(1 min), then you get exactly 10 samples. However, I agree "precise thread group" sounds weird. Vladimir
