[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 11:35:55 CEST 2016
Hi Cristel, hi Robert, Thanks a lot for your feedback. 1. @Cristel, yes, you’re right, I’m aware of this scheduling issue. Indeed, a big part of such ‘abnormal’ intervals is reasonably ‘short’, 55% are between 2 and 4 planned value, among 510 cases seen in 1074 probes traces over a week’s time. 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? Again many thanks. Regards, wenqin > On 02 Sep 2016, at 09:53, Robert Kisteleki <robert at ripe.net> wrote: > > 479 is almost exactly twice the frequency (240), so it's basically one > result skipped. Most likely the probe just didn't execute that measurement > (was powered down? rebooting? was refreshing its set of tasks just at the > worst time?) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20160902/1c77d36d/attachment.html>
- 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 ]