Explain core count recommendation #13
Labels
No labels
documentation
good first issue
help wanted
resolution: duplicate
resolution: invalid
resolution: won't fix
status: needs triage
type: bug
type: feature
type: performance
type: question
version: 1.19.4
version: 1.20
version: 1.20.1
version: 1.20.2
version: 1.20.4
version: 1.20.6
version: 1.21.11
version: 1.21.4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Minecraft/Folia#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The FAQ says:
How did this answer come about? Why "at least 16" and not 8 or 4? It confuses me because I would think anything > 1 would be an improvement over the single-threaded implementation.
Thanks.
Because the entire system needs more threads to manage the work for the threads, and then you've gotta actually have those regions do stuff, which depend on other systems which have their own threads, etc
the vanilla server software may use a single thread for the main tick loop, but, it has many other threads, and if you only have 1/2 cores, you'll be stealing time away from the main thread. The number here generally is based on internal testing with limited hardware accessibility as well as seeing how it performs (and doesn't) on the small amount of hardware we have access to. it might perform well on less cores for some use-cases, but, that's not something we can promise/test, ymmv.
Thank you for the explanation!