Multi-process servers
- Dominant language
- C
- Stars
- 125
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
With `SO_REUSEPORT`, many processes can listen on the same port at the same time. Running several instances of the Go server might reduce the overhead of Go's `epollwait` as @jbardin points out in [this reply](https://groups.google.com/d/msg/golang-nuts/fuKOlm5CAdM/t7IIplQYqPAJ) on golang-nuts. This issue tracks that idea.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Go server and its socket setup, then read how the current process accepts connections. Investigate the SO_REUSEPORT and epollwait idea described in the issue and determine the expected multi-process behavior. The issue does not define acceptance criteria or tests, so the done state needs clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100