모든 토론으로 돌아가기
error: timeout
jiri.bauer
3 वर्ष पहले
Hello,
We are using your bulk whois method to retrieve info for about 500k of .sk domains. We are forced to make at least 1 minute breaks between two consecutive requests otherwise we are getting a lot of “error: timeout” results (even with 1 minute breaks we usually get one or two errors among 15 results in one request).
Is there a way to increase the throughput of these results? With this rate we aren’t even close to being able to consume our daily limit of requests.
Best regards
Jirka Bauer
아래에 의견을 추가하고 토론에 참여하세요.
새 댓글을 게시하려면 로그인 / 가입
BTW, the new batch API is rolled out. Check it out: https://rapidapi.com/backend_box/api/bulk-whois?endpoint=apiendpoint_f002c6f0-86e8-4db4-b28c-cebc4f76a8ec
Apologies. We are having some scalability issues. The new version is to be fully batched. The idea is that you “enqueue” N say 500 domains and have them being processed. You come back with a batch id and once ready you fetch the whole batched result set. This way there is no timeout issue. Of course it takes a while to process it and you have to “poll” to see if that is complete yet. Would that mode of API be useful for you?
We are on the Ultra plan. Which means we should be able to query 3000 x 15 = 45000 domains per day. However we are forced to make no more than 1 request per minute (because of all the timeouts) and usually we got about two timeouts per request. That means we are able to get results for about 60 x 24 x 13 = 18720 domains per day.
To your last question - we need the whole whois data.
Jirka Bauer
Hi,
What plan are you on? What number of domains do you need to query a day? Do you need it for availability or WHOIS data?
thanks,
PB