WIP: [core] let OS control affinity of threads as opposed to manually setting #2571
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "liz-thread-competition-experiment"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This will make the CFS in Linux kernels be happy (as marking too many threads as critical actually reduces performance). The load balancing gets distributed evenly across the 4 cores which will outperform in a 8-core setup system. We still have over 40 threads but this SHOULD help to reduce thread contention (especially since the CPU thread is one of the most important to run). The scheduling should be ideally left to the OS as most of them have decades of running proficient scheduling algorithms which likely outperforms any hand-made solutions.
Signed-off-by: lizzie lizzie@eden-emu.dev
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
[core] give exclusive affinity control to CPU threadsto WIP: [core] give exclusive affinity control to CPU threadsWIP: [core] give exclusive affinity control to CPU threadsto WIP: [core] let OS control affinity of threads as opposed to manually settingView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.