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
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
The max number of overall connections in the native layer is limited by the number of concurrent virtual sockets: each virtual socket adds an entry to RunLoop and the max number of entries per process is 64, that is enforced by the OS.
Adding more than 64 entries doesn't trigger an error in RunLoop, simply the entries after the 64th will not be scheduled until other entries have been removed.
Given one entry in RunLoop is alrady taken for another workitem, it would be safe to limit the max virtual sockets to 62.
The text was updated successfully, but these errors were encountered:
The max number of overall connections in the native layer is limited by the number of concurrent virtual sockets: each virtual socket adds an entry to RunLoop and the max number of entries per process is 64, that is enforced by the OS.
Adding more than 64 entries doesn't trigger an error in RunLoop, simply the entries after the 64th will not be scheduled until other entries have been removed.
Given one entry in RunLoop is alrady taken for another workitem, it would be safe to limit the max virtual sockets to 62.
The text was updated successfully, but these errors were encountered: