Conn.Read is a much higher level construct the using the syscalls directly.
The largest part of the overhead is coordinating with the network poller.
There's also a slight overhead of using the net.Conn interface, so
asserting the value to a *net.TCPConn may save you a little (though I'm not
certain how much of a difference that makes in recent releases).
Using the syscalls, you're essentially dedicating a single OS thread to
handle that socket's IO.
On Wednesday, November 30, 2016 at 2:13:10 PM UTC-5, anto...@gmail.com
> Any thoughts, anyone?
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.