Significant RAM Increase when increasing scheduler threads
Hello, I have been trying to use the DHS Paper plugin (the snapshot 0.9.0 version) and have been having a rough time getting it running properly... I used to think our server was really beefy and powerful, but this plugin has began to make me reconsider my opinion haha
The configuration entries that might be applicable here are:
The main item I have tinkered with is the scheduler_threads. When I leave it at 2, the servers memory usage stays very low - we have 20Gb allocated towards the server, and when running the pregen with 2 threads, it goes from 2 to 4Gb of usage. When I change the scheduler_threads to 4, the pregen completely kills the server - it will eat all the remaining memory within 10 seconds of starting the pregen command.
I have tried using the different jvm startup arguments, first, I tried the "high memory/core count" configuration; when that didnt work, i tried the low/mid memory count arguments and ran into the same problem.
Solution:Jump to solution
New development, when I change from fast over world builder to FullBuilder, it behaves fine. Works with 8 threads
10 Replies
Sorry for the nudge, but if any of the developer(s) has a moment to maybe take a look to help me diagnose my issue, that would be appreciated
I have no idea why that would happen. Please post full mod and datapack list.
And flags
We have the extended height data pack installed, other than that, the other plugins we have are mostly just for the operation of our build server. Let me grab the full list
Essentials, Dynmap, CoreProtect, Luckperms, multiverse, worldedit, worldguard, and worldborder are the main ones aside from the DHS plugin. We have some other plugins that provide random little tidbits in the game, but none that consume additional significant resources.
Before I start pregen, I disable the map rendering for dynmap
And as for worlds I have loaded, we only have 2 worlds loaded on the server. First is the main build world, the other is just a super flat world.
Changing to 3 scheduler threads makes it not consume an absurd amount of ram.. 4 scheduler threads makes it just eat it all up in seconds
Solution
New development, when I change from fast over world builder to FullBuilder, it behaves fine. Works with 8 threads
So maybe it’s a FastOverworldBuilder issue?
I think this estimate might be capped at an integer? Lol I also think I might not be able to complete this lod rendering in a reasonable amount of time
Wut, is your world 20k x 20k blocks?
Also, how old is your nightly version?
I got it Friday I believe.
And yes, just about. It’s 15k x 13k.
is the LOD on the server is stored differently (different db format/structure) than an LOD generated on the client?
because im curious, i have the entire LOD for this world loaded on my local machine with only about 2gb of space being used... it would be significantly more time efficient if i was just able to load the sqlite file I have on my local on the server
Plugin and mod db formats are not the same
naive question, is there any particular reason the formats are different?