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] Actual measurement interval much larger than planned
- Previous message (by thread): [atlas] Actual measurement interval much larger than planned
- Next message (by thread): [atlas] Reminder: Join RIPE NCC IXP Tools Hackathon, 22-23 October, Madrid
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Sep 2 12:57:17 CEST 2016
On 2016-09-02 12:20, Wenqin SHAO wrote: > Thanks for confirming. The specified frequency is indeed well respected. When there is no data-missing, the interval shift rarely exceed 14s, small compared to 240s the scheduled interval. > What intrigues me is that the exact phase/timing is as well kept after power cut and reboot. The probes have a crontab-like mechanism to remember what they need to do. As long as their clock is more or less ok, they will stick to the pre-allocated times and tasks. > By the way, can a measurement be as well skipped, as designed behaviour, due to scheduling issues mentioned by @Cristel? We're trying to avoid overloading probes, but not everything is under our full control. Some measurements can pile up; Cristel & Randy & co. had a paper about the observed (worst-case) behaviour. Regards, Robert
- Previous message (by thread): [atlas] Actual measurement interval much larger than planned
- Next message (by thread): [atlas] Reminder: Join RIPE NCC IXP Tools Hackathon, 22-23 October, Madrid
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]