Ideal timeout period for dns lookup -
In my rail app, I do a nslookup using Ruby Library resolv
. If it is too long to solve the site like dgdfgdfgdfg.com
in some cases such as 20 seconds (mostly for non-existent sites) because it applies due to recession So though I have to start a timeout period for DNS lookup. What would be the ideal timeout period for the DNS lookup so that the actual site's resolution fails. Will something be fine like 10 seconds?
You can find some tests among users, compromising with the correct number of accountability / execution.
In addition to that, you can adjust the time on the basis of network traffic.
For example, for every successfully revolue
, how long do you take to reserve it? And every hour (for example) you can calculate the average and set its value doubled as a timeout (remember that "average", broadly speaking, "middle"). This way, if your latency is high on some point, it automatically adjusts itself to increase the timeout period.
Comments
Post a Comment