[Paper] Render threads config option not respected.
Frerduro opened this issue ยท 4 comments
Basically what the title says. "max-render-threads" is not actually restricting the number of threads used.
Are you sure you're not confusing this option for a global thread count? The config option is per-world, and it seems to work fine in my testing.
I am referring to the options in config.yml even after setting them to 2 squaremap still uses ~29-30 cores/threads of a 5950x to render the map. Am I possibly mis-understanding this? I know the wiki says jvm threads but surly setting it something low to something like 2 will restrict how much of a cpu it uses just a little?
world-settings:
default:
map:
enabled: true
display-name: '{world}'
icon: ''
max-render-threads: 2
iterate-up: false
max-height: -1
lava:
checkerboard: true
biomes:
enabled: true
blend-biomes: 3
glass:
clear: true
water:
clear-depth: true
checkerboard: false
zoom:
maximum: 3
default: 3
extra: 2
background-render:
enabled: true
max-chunks-per-interval: 1024
interval-seconds: 15
max-render-threads: 2```
The config controls the render worker thread pool size, however other thread pools are used by the server itself to load chunks and etc. You can use the commands jps
and then jstack <pid>
to get a thread dump showing what every thread is doing if you want to confirm the count of squaremap render threads.