Consider setting CPU affinity for fdbserver processes
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
From https://forums.foundationdb.org/t/setting-cpu-affinity-for-fdbservers/84, it was noted that we don't set CPU affinity for any of the processes we start, and there's likely advantages to doing so. It appears once upon a time, we had code in the resolver that would pin itself to a core, but it was commented out, and I agree doing it from fdbmonitor sounds like a better solution.
Implementing this doesn't sound like too much work, and a quick run through a performance test should tell us if it makes any noticeable impact.
Contributor guide
Research direction
Start with fdbmonitor, which the issue identifies as the preferred place to set CPU affinity for processes it starts, and review the previously commented-out resolver affinity code for context. Run the project's performance test after implementing the behavior and confirm whether CPU affinity produces a noticeable impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100