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 was archived by the owner on May 24, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on May 24, 2022. It is now read-only.
We saw segfaults occurring when stud attempts to handle more than 65k connections to a single backend (src/dest tuple limit). We got around it by sharding across 127.0.0.2, 127.0.0.3, ... fronted by the same stud instance.
Activity
vikrum commentedon Jan 28, 2013
We saw segfaults occurring when stud attempts to handle more than 65k connections to a single backend (src/dest tuple limit). We got around it by sharding across 127.0.0.2, 127.0.0.3, ... fronted by the same stud instance.