[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] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wenqin SHAO
wenqin.shao at telecom-paristech.fr
Fri Sep 2 12:20:04 CEST 2016
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. By the way, can a measurement be as well skipped, as designed behaviour, due to scheduling issues mentioned by @Cristel? Thanks, wenqin > On 02 Sep 2016, at 11:45, Robert Kisteleki <robert at ripe.net> wrote: > > >> 2. As observed by @Robert, most ‘abnormal’ interval is actually very close >> to integer times of planned value. >> If I get your message right, you are indicating that planned measurements >> can be skipped for the reasons you mentioned and shall kick-off again >> following the previous timing, even after rebooting? > > Kind of. There's a reasonable expectation that probes will measure with the > specified frequency, but reality is that for various reasons you'll not see > all the results all the time. > > Regards, > Robert
- Previous message (by thread): [atlas] Actual measurement interval much larger than planned
- Next message (by thread): [atlas] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]