Perhaps too late but a thought...

[kualojo]

As I understand things each batch, the DAC is checked to see success, and then it waits for the next batch to process. Any domains not yet registered are then processed in the next batch / minute.

The problem is that between that DAC check, and the next minute, many of the domains could be registered in between (and this may be up to a minute later).

This means that we're wasting valuable requests on already registered domains.

It strikes me that the DAC check should run just before and as close as possible to the next minute's send request so that we know that the next batch of domains are actually available for registration, and don't bother sending requests for domains which may have been registered by other registrars in the near minute after the previous DAC check.

Anyway, it's probably a bit too late to do anything about this for today but wanted to share just in case.

[AaronClifford]

You could probabaly add an additional sleep somewhere, but yes a little late now

…

On Fri, 5 Jul 2019, 08:10 kualojo, ***@***.***> wrote: As I understand things each batch, the DAC is checked to see success, and then it waits for the next batch to process. Any domains not yet registered are then processed in the next batch / minute. The problem is that between that DAC check, and the next minute, many of the domains could be registered in between (and this may be up to a minute later). This means that we're wasting valuable requests on already registered domains. It strikes me that the DAC check should run just before and as close as possible to the next minute's send request so that we know that the next batch of domains are actually available for registration, and don't bother sending requests for domains which may have been registered by other registrars in the near minute after the previous DAC check. Anyway, it's probably a bit too late to do anything about this for today but wanted to share just in case. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=AAGRD7OLLQIMZDA7EBGY4RTP53XYBA5CNFSM4H6IGWDKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5PUZKQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGRD7OKEYMSQIUUWAIDUR3P53XYBANCNFSM4H6IGWDA> .