One-offs are not intended to be used like this. The emphasis with them is to schedule as quickly as possible *no matter what*. This is for quick look-see work. Not for repeated measurements on the same set of probes. If you want to schedule that much from an indentical set of probes, do not use one-offs. Daniel On 11.05.16 13:57 , Paul Vlaar wrote:
Same thing here, I just did another test. Ran 7 UDMs in parallel for SOA ripe.net @ manus.authdns.ripe.net, the result of one of those:
https://atlas.ripe.net/measurements/3793292/#!probes
Compared to running another one, but on its own w/o scheduling others in the same run:
https://atlas.ripe.net/measurements/3793293/#!probes
I'd call this a bug, or at least something to somehow work around, but not sure how, yet.
~paul