We have a major problem that’s postponing the launch of our server - we’re running the latest Sponge on 1.10.2 and we’re constantly hitting 100% RAM even with only 4 players on. We’re running Pixelmon, but that shouldn’t cause the problems that are occurring.
We managed to get chunks to unload (they were never unloading before), but RAM usage is never going down. The server is with NodeCraft, and the server has 4GB of RAM. If I leave it on overnight, with only around 4 players, it’ll go way past the 4GB and need a restart.
chunk-gc-load-threshold=100
# The tick interval used to cleanup all inactive chunks that have leaked in a world.
# Set to 0 to disable which restores vanilla handling. (Default: 600)
chunk-gc-tick-interval=150
# The number of seconds to delay a chunk unload once marked inactive. (Default: 15)
# Note: This gets reset if the chunk becomes active again.
chunk-unload-delay=15
This is the part of our sponge config with garbage collection, we made the values quite low to force some collection to happen.
What operating system are you using? 4GB is going to be a limiting factor if you’re running and OS like Windows (or Linux with a GUI). From experience… If you must do this then make sure you are running the server edition of Linux, like Ubuntu server, which is the non-GUI version and will run in a footprint of a few hundred MB. That maximizes the memory for Minecraft servers. You can allocate up to 3.5GB for Minecraft with this setup compared to less than 1GB for Windows or Linux O/S with a GUI. Eithe rway, you need to run some numbers to properly size the server in terms of how many players you want to support and the type of O/S you plan to use. From what you describe… it sounds to me like you’re running your server on an O/S that is using most of the memory for itself, which is what I encountered when running my first server on Windows with 4GB of RAM.
I run a Pixelmon server without any issue using the following combo and never had to tweak anything. Not sure why you think there’s a need to fore chunk loading/unloading. That’s just going to get you into trouble.
Memory doesn’t discriminate against what OS is being used.
What will determine the memory usage is use of memory. So, unless it has already been resolved, why not enumerate two things:
The actual command line used to start the server. I.e., which flags are passed to the Java JVM.
The list of mods/plugins that are in your mods/ folder.
Anecdotally, 4Gb is on the low side of memory headroom to run a MC server. But answering the two questions above, and then researching the ways you can tailor the JVM to treat memory usage, plus being economical with the plugins/mods you choose may reveal the answer to your question.
Just wanted to post an update for everybody here, as the co-owner of this server.
Our issues were caused by WorldEdit, and were two-fold; RAM use would rise steadily when WE wasn’t being used (but was loaded), and would spike up after using certain commands. This wasn’t entirely reliable; sometimes nothing would happen, sometimes it’d spike right away, sometimes it’d jump up minutes after the last WE command was used. Removing WorldEdit almost completely stabilized RAM use. We’re still doing some testing here, but I think this topic can be closed.
(I’ll see if I can get Xenoyia to reply, he’s been pretty busy)
