You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using windows server on my production enveronment. Main question is there any limitations in library for 250~ simultanious connection? I've noticed that my worker will not open any more connection than that.
Or is this the windows limitations?
The text was updated successfully, but these errors were encountered:
@Geckon01 This sounds like a limitation to me and I think this has something to do with the amount of sockets you're using at the same time. I researched a little bit and stumbled upon an issue in reactphp/socket which sounds pretty similar to the problem you're describing: reactphp/socket#198. I think there's a lot of input in there which should lead to a conclusion.
On Unix platforms, this constant is usually defined as 1024, so it's much less of a problem here. As an alternative, you might be able to use one of the alternative loop implementations which provide ways to work around this limitation (e.g. using thread-pools to select() no more than 64 sockets per thread ref).
I don't know what you're seeing exactly and I'm not sure what defaults you're using on your production environment, I think trying to change FD_SIZE or using a different loop implementation should be a good start to solve this issue.
I believe this should answer your question, so I will close this ticket for now. We can reopen this if you encounter the same issues again after trying out the solutions mentioned in here. If you do need to reopen the ticket, please provide some information about the steps you've taken so far, what worked and what didn't.
I'm using windows server on my production enveronment. Main question is there any limitations in library for 250~ simultanious connection? I've noticed that my worker will not open any more connection than that.
Or is this the windows limitations?
The text was updated successfully, but these errors were encountered: