3 ms·
In-process caches of DNS replies would solve it (they don't have to last for long, 1 minute is enough). Doesn't libcurl do that by default? Federating the inte
by marcosdumay 6y ago
In-process caches of DNS replies would solve it (they don't have to last for long, 1 minute is enough). Doesn't libcurl do that by default?
Federating the internal DNS would solve it. Who creates a DNS system without redundancy?
A keeping the connections open for each process would solve it. But then, you'd need HTTP/1.1 or newer, maybe that's too new.
In fact, that scenario requires breaking about every good practice for the tools used. Yet the author mainly blames the lack of threads. Yeah, sharing that coordination info would increase your scale by some 10x, while creating a lot of other unrelated failure modes.