[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] Taking the fuzz our of client cache results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Sat May 17 20:59:09 CEST 2014
Hi Mark, On 2014/05/17 20:24 , Mark Delany wrote: > Also, a pre-primed query would presumably cost twice as many credits since > it's really running two queries. > > Do others think a primed cache query is of use? And, are there ways of > achieving this already? I'm just focusing on what is already there. If you are using oneoffs, then just running two oneoffs a minute apart should do what you want. 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. Philip
- Previous message (by thread): [atlas] Taking the fuzz our of client cache results
- Next message (by thread): [atlas] Taking the fuzz our of client cache results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]