curl-library
Re: Multiple DNS resolution threads are spawned for same host/port for a multi-handle
Date: Mon, 27 Mar 2017 19:53:56 +0530
Hi Daniel,
Thanks for your update.
Just to clarify about the cpu usage, the resolution threads don't
themselves take 100% cpu. They spike the cpu usage by 30-40% for 10 to 15
seconds.
Again you mentioned that you are considering thread pool for DNS
resolution. Any idea when that would be available?
Thanks
Mandar
On Thu, Mar 23, 2017 at 3:20 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Wed, 22 Mar 2017, Daniel Stenberg wrote:
>
> If a name resolve has been initiated for name NN and a second easy handle
>> wants to resolve that name as well, make it wait for the first resolve to
>> end up in the cache instead of doing a second separate resolve.
>>
>
> It struck me that we could also consider redoing the threaded solution
> somewhat more and perhaps have a thread-pool with N threads for name
> resolves and they could stay alive during the multi handle's entire life
> time so that we don't have to start/kill threads to the extent we do now
> and we could get away with less threads than number of simultaneous easy
> handles.
>
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-03-27