net: Allow setting socket options with DialTCP #34743
Previous scale testing has shown that
For performance reasons, we also need to set socket options within this same codepath.
Today, it looks like we only have 2 options:
Is the Go team open to exposing some way to use
The text was updated successfully, but these errors were encountered:
What performance numbers do you see between the two?
Can you summarize where you're seeing the performance loss between Dial and DialTCP? #18601 looks like it's kinda long and about an old Go version and talking about things that are common to both Dial and DialTCP.
If the main cost is resolving the ip:port from the name, can't you do that first, and then just call Dial with the string-ified IP:port? That'll at least skip DNS.
Before we add new API (e.g. Dialer.DialTCP), we'd really want to understand the problem first.