This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] probe congestion?
- Previous message (by thread): [atlas] New on RIPE Labs: Using RIPE Atlas to Debug Network Connectivity Problems
- Next message (by thread): [atlas] probe congestion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Vlaar
pvlaar at afilias.info
Wed May 11 12:25:53 CEST 2016
Hi all, while running a DNS UDM on a fixed set of (reused from a previous UDM) probes, I noticed the following. When I start 6 UDMs against the same set using the web UI, as a one-off measurement, starting "now", the RTTs for all of the measurements shoots up on all of the probes (500-1000+ ms). When I start the 6 tests individually, the RTTs are much lower, and close to what I'd expect them to be. It appears to me that when multiple UDMs are scheduled on the same probe, these should be run in serial, not parallel, in order to not run into congestion issues. Or am I simply expecting the wrong behaviour, and should I not schedule one-off measurements in parallel in the first place? ~paul
- Previous message (by thread): [atlas] New on RIPE Labs: Using RIPE Atlas to Debug Network Connectivity Problems
- Next message (by thread): [atlas] probe congestion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]