--
You received this message because you are subscribed to the Google Groups "dnsruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dnsruby+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dnsruby/82d5b208-0a04-49f5-a106-51b145225852%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi -As per some of the example code, it’s best to limit the number of concurrent queries. The idea is to send up to a maximum, and then send more as previous queries complete. This effectively creates a buffer of concurrent queries.HTH,Alex.
On 21 Apr 2016, at 17:09, Keith Bennett <keithr...@gmail.com> wrote:
Hi, Alex and All -
I'm trying to help out a poster on Stack Overflow, at http://stackoverflow.com/questions/36743801/increasing-ruby-resolv-speed.
I've suggested he use dnsruby in a script I wrote for him (at https://gist.github.com/keithrbennett/3cf0be2a1100a46314f662aea9b368ed), and he's getting some errors and 100% CPU utilization when processing 5,000 subdomain prefixes and 1 domain. We're not sure yet if it's in the dnsruby code, but should there be any problem posting 5,000 asynchronous requests to a queue and then retrieving the responses? No, right?
- Keith--
You received this message because you are subscribed to the Google Groups "dnsruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dnsruby+unsubscribe@googlegroups.com.