I can't see how a large number of waiting goroutines would cause an
increase in the number of OS threads, which was the OP's original problem
(hitting the 10,000 thread limit)
What the OP is implying - but we have not seen good evidence for yet - is
that in some circumstances a non-blocking con
On Fri, Feb 9, 2024 at 2:10 PM Ian Lance Taylor wrote:
> On Fri, Feb 9, 2024 at 11:57 AM Kurtis Rader wrote:
> >
> > The connect() syscall is normally blocking. It doesn't return until the
> connection is established or an error occurs. It can be made non-blocking
> by putting the file-descripto
On Fri, Feb 9, 2024 at 11:57 AM Kurtis Rader wrote:
>
> The connect() syscall is normally blocking. It doesn't return until the
> connection is established or an error occurs. It can be made non-blocking by
> putting the file-descriptor into non-blocking mode before the connect() call.
> Howeve
The connect() syscall is normally blocking. It doesn't return until the
connection is established or an error occurs. It can be made
non-blocking by putting the file-descriptor into non-blocking mode before
the connect() call. However, that then requires either an async callback or
another syscall
