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/ripe-atlas@ripe.net/
[atlas] Taking the fuzz our of client cache results
- Previous message (by thread): [atlas] Taking the fuzz our of client cache results
- Next message (by thread): [atlas] NTT Communications (US) joined RIPE Atlas anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Delany
f4w at echo.emu.st
Sat May 17 21:57:29 CEST 2014
On 17May14, Philip Homburg allegedly wrote: > If you want a periodic measurement then we have an (apparently > undocumented) option to prefix the query with the probe's ID and the > current time. This should also give the desired effect. It helps a little wrt probes sharing caches, but it doesn't help with the timing being distorted by the cache having to fetch parent records. For example, the cache having to ask .com to get example.com name server details. Even if parents have long TTLs (e.g. they come out of a TLD) there is no guarantee that the parent records haven't been evicted due to caching pressure. And yes, periodic is what I should have clarified. Mark.
- Previous message (by thread): [atlas] Taking the fuzz our of client cache results
- Next message (by thread): [atlas] NTT Communications (US) joined RIPE Atlas anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]