Once something is buffered, it can not be unbuffered. That is, the latency of the I/O operations permanently increase with respect to the properties of the buffering done underneath. Go does not buffer things by default because not everyone wants to buffer things by default. This is also why Nagle's algorithm is off by default in the network stack. These are good things: you can always buffer to get better throughput, but you can't decrease latency.
On Wednesday, August 30, 2017 at 5:44:46 AM UTC-7, Nilsocket wrote: > > I have seen that python input and output is buffered, but golang's input > and output is not buffered. > > For those types of problems where i need to take large amounts of input, > It's taking long time to just take input than to do processing. > When we have advantages with buffered input and output, why isn't it input > taken in such a way while I'm using scanf function. > or else am I supposed to use bufio package whenever I want to take > buffered input and buffered output. > > Thank you. > -- 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. For more options, visit https://groups.google.com/d/optout.
