On Sun, Jun 21, 2020 at 8:05 PM Robert Engels wrote:
> Most webservers use multiple threads per socket - this is commonly
> observed with async IO. IO in Go is async behind the scenes so you don’t
> need to worry about this. You probably will use a Go routine to read the
> socket; and probably
Most webservers use multiple threads per socket - this is commonly observed
with async IO. IO in Go is async behind the scenes so you don’t need to worry
about this. You probably will use a Go routine to read the socket; and probably
another to do the writing - so you can treat the IO as
On Sun, Jun 21, 2020 at 5:11 PM wrote:
> Yes, the exact use case I'm thinking of is reading UDP datagrams. I just
>> want to read them as fast as possible then hand them off to other
>> goroutines for further processing. I was just thinking I would get better
>> speed/throughput if I had a
>
> Yes, the exact use case I'm thinking of is reading UDP datagrams. I just
> want to read them as fast as possible then hand them off to other
goroutines for further processing. I was just thinking I would get better
speed/throughput if I had a couple of go routines listening, waiting to
Can you have multiple go routines waiting to read from a socket, or are you
limited to just one?
--
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
