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] When to consider a measurement finished
- Previous message (by thread): [atlas] RIPE Atlas Software Probes Survey
- Next message (by thread): [atlas] When to consider a measurement finished
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wouter de Vries
w.b.devries at utwente.nl
Tue Jun 18 20:08:23 CEST 2019
Hi all, I am currently trying to do some measurements according to the following steps: 1. create a one-off measurement 2. wait for it to finish, by periodically polling the msmid and checking the status. 3. fetch the results However, the system takes a pretty long time to set the status to finished, even when all results are already in (maybe 10 minutes?). What heuristics/method do you recommend to determine whether to consider a measurement as finished? One option I consider is to periodically fetch all results for a given msmid and checking if the number of results matches the number of probes assigned to the measurement. However, I suspect that causes a much higher load on the infrastructure. Best regards, Wouter de Vries
- Previous message (by thread): [atlas] RIPE Atlas Software Probes Survey
- Next message (by thread): [atlas] When to consider a measurement finished
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]