On 2019-01-24 06:39, Christopher Morrow wrote:
> howdy!
> So, if I have a dns server somewhere and I want to make a bunch of
> measurements:
> "how does NYC see my dns?" (pick N probes near NYC)
> "How does DEN see my dns?" (pick N probes near DEN)
> "How does LHR see my dns?" (pick N probes near LHR)
> "how does ...."
>
> ...you get the idea... I'm trying to characterize my service from a
> 'user' perspective by large Metropolis, well within N km of that
> metropolis anyway :) but across ~70 or so metros, in v4 and v6 and with
> authoritative and non-authoritative queries with each test running for 4
> days so i can see some daily cycles in traffic patterns/etc. The number
> of measurements is large in total, breaking up by 3-4 metropolis chunks
> is super tedious :(
>
> Can I request an API key (or some other thing) which can make that sort
> of request happen for all my measurements in one go? The thing I'm
> probing is very able to handle a few extra thousand queries per second..
> and I'd only be hurting myself i get my estimate wrong :)
>
> thanks!
> -chris
Hi,
Note taht we have a large amount of measurements already against
8.8.8.8, 1.1.1.1 and such, perhaps reusing data from these is an option?
perhaps. I can go digging. i was/am particularly interested in performance for v4/v6 cached/not from the same vantage point at as nearly the same time.
I didn't think that was going to be fruitful in searching existing measurements :( I should have taken a bit longer to dig though.
(I'd be particularly happy if it was, since one of the very reasons we
wanted to make this whole network really open is to be able to reuse
data from others' measurements.)
If that's not possible, then I'd advise you to run a small script that
issues a measurement request and parametrises it with cantage point /
target pairs, and use an API key for it. Perhaps also ask for a quota
increase first :-)
I have this script, but I need to have something that runs over many days (or maintains state) and issues the measurements at a pace which maximizes my measurement speed and minimizes my inolvement :) It wasn't apparent that the restriction I'm seeing is 'per api key', I thought it was 'per target'.
Cheers,
Robert