On Tue, Dec 31, 2019 at 7:23 AM Ron Wahler <ron.wah...@gmail.com> wrote: > > How much of the read behavior is in the golang underlying code on the read > and how much is > on the underlying OS driver that implements the behavior of the read. I > understand the stream nature of the TCP connection and I handle that in my > code, I was just looking to optimize the buffer allocation for the read on > each packet of the stream so I don't have to over allocate the buf if I > scaled out my function to be concurrent. From the responses so far I think I > just have to pick a buffer size for the Read() or the ReadAtLeast() and just > process multiple buffers with my pre-allocated guess on the buffer size as I > am already doing.
You may be interested in the discussions at https://golang.org/issue/15735. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVkQN-Dkbtvn%2B%3DGmmZL-gEsEGAWcq-cxK0-Yh6Y-F4z1g%40mail.gmail.com.
