Added render threads option #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Each time ChunkBuilder.startWorkers() is called, which happens on each f3+f, a certain number of Chunk Render Task Executor threads are created. By default this is Runtime.getRuntime().availableProcessors(), which results in 32 render threads constantly being recreated for CPUs with 32 logical processors. Reducing this number to 1 significantly improves performance of F3+F, with no obvious impact on rendering performance. An option for 1-32 has been added to the settings,
but I suspect the default of 1 will be optimal for everyone.Upstream logic for calculating default thread count has been added, users can choose to override