Download
Browse source Changelog
Documentation
Project   Bug Bounty   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users Mailing lists Book: Everything curl Video presentations Report a bug Paid support
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: bypassing name resolve hangs

From: Dan Fandrich via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 23 Sep 2019 15:19:22 +0200

On Mon, Sep 23, 2019 at 02:39:15PM +0200, Paul Dreik via curl-library wrote:
> Is there an easy way to (locally) add a hack to get the resolving done
> quicker? Perhaps by hard coding everything to resolve to a fixed adress?
> The fuzzing speed is below 100 tries per second, and that is at least a
> factor of ten too low.

I wrote a test program that resolves a name found in /etc/hosts and it does
70K lookups per second. If you disable curl's threaded resolver and configure
the system resolver to only look in /etc/hosts (and not to go to the network
for anything) then I would expect that would eliminate getaddrinfo() as the
bottleneck.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-09-23