DAC query limits

ian · Aug 14, 2014

Am I the only one befuddled by DAC query limits! I thought for the hours you didn't poll you were effectively re-charging your allocation, but it seems that you effectively get back what you put in exactly 24 hours. But what happens if say you used your allocation at midday, which is then put back in the following day, but you don't use it then but later in the day, does that same allocation appear at midday the next day or only later when you started using it?

Also, Nominet mention that if you close and re-open a connection (possibly to make changes) you incur a 3 second penalty. Does anyone know if this 3 seconds is just on the initial query, or all queries, and if so, over how long would this delay continue?

Darren · Aug 14, 2014

Its a rolling 24 hours and the delay is only upon connection.

dropcycle · Aug 14, 2014

ian-d said:
Also, Nominet mention that if you close and re-open a connection (possibly to make changes) you incur a 3 second penalty. Does anyone know if this 3 seconds is just on the initial query, or all queries, and if so, over how long would this delay continue?

The 3 second delay is for each new (socket) connection to the server. It's the connection that incurs the penalty not the query.

Skinner · Aug 15, 2014

Its rolling 24 hours, its a little hard to get your head around but simple put lets say you poll at 200ms/5x from 12:00

12:00 - 18,000ph
01:00 - 18,000ph
02:00 - 18,000ph
the name frops at 02:59:59

You now have about 380,000 until 11:59:59.

At 12:59:59 you'd have recovered the 18,000 use earlier in the day.

So if you ran at 100ms/10x from midnight tonight, youd run out at midday today, and you would be unable to poll again until midnight tomorrow, when you could poll at 100ms/10x or less.

ian · Aug 15, 2014

Thanks. Does polling 5 domains on any given day slow down the query lookup versus just polling a single domain?

dropcycle · Aug 15, 2014

ian-d said:
Thanks. Does polling 5 domains on any given day slow down the query lookup versus just polling a single domain?

No.

Querying 5 separate domains is the same as querying the same domain 5 times. There is no reduction in speed unless you breach the daily (rolling) limits.

ian · Aug 15, 2014

So there would be no advantage to querying a single domain at 150ms versus five domains at the same 150ms?

dropcycle · Aug 15, 2014

ian-d said:
So there would be no advantage to querying a single domain at 150ms versus five domains at the same 150ms?

Correct. But if you do either at 150ms for a full 24 hours you would breach the daily limit of 432,000 for Real Time queries.

Do the same at 200ms and you're fine.

AssetDomains · Aug 15, 2014

ian-d said:
So there would be no advantage to querying a single domain at 150ms versus five domains at the same 150ms?

Not exactly the single domain would be pinged every 150ms if you query 5 as you said each individual name is only being checked once every 750ms so you have way more chance doing one individually.

Murray · Aug 15, 2014

dropcycle said:
Correct.

Wait what?

I didn't that was was correct at all

I thought you query one name at a time.. so if you were chasing 150ms for two domains, you would check the first, then 150m later the next.. so you're effectively chasing twice as slow for both as you would for one?

ian · Aug 15, 2014

That is what I thought and think that is what dropcycle meant in a round about way. I know about the 432,000 limit, thanks for the clarification.

dropcycle · Aug 15, 2014

ian-d said:
... think that is what dropcycle meant ...

Yes

DaveP · Aug 15, 2014

The others are correct. Rotates is n amount slower than single (n being number of domains). So if you got 3 domains on rotate at 125ms for example, each domain is only being checked once every 375ms, this massively reduces your chances. For the best chance, singular burst is best.