tchieze Posted June 3, 2014 Posted June 3, 2014 Hey guys, I've been having some memory issues with my Tekkit Server. I'm running it in Gentoo Linux with a scarce 3GB of ram (yes, I know it isn't too practical, but it's what the server has). After the server has fully initialized, total memory use hits around 1.4GB, and when a couple users log in, it hits ~ 1.5-1.6GB. It seems problems arise when the users disconnect and reconnect, as, apparently, the memory from their previous session is not released. Within a few hours of login-cycling, the server, only having been used by the same two players, causes memory use to approach swapping range (around 2.5G). Has anyone here had experience with this problem, and, if so, can you offer advice on how to potentially fix it? Thank you in advance. Quote
Discord Moderator plowmanplow Posted June 3, 2014 Discord Moderator Posted June 3, 2014 (edited) There isn't enough information there to truly isolate the problem, but here is some information that might help: One should never allocate the amount of physical system RAM to a Forge/MC server process. If your physical server (or virtual, whatever) has 3G of ram then you shouldn't allocate more than 2G to the java process (-Xmx2048m) and I would personally start at 1.5G. This provides overhead space for the operating system to do its thing for all of the processes it has to manage like its own memory management, network I/O, file system operations, etc. It is advisable to reduce the number of chunks loaded around each player. This is controlled through the "view-distance" setting in your server.properties file. I would recommend setting it to 6 and seeing how things change. Limit the use of force-loaded chunks using various chunk loaders. You can use the /chunkloaders command to see the number of forced chunks in each dimension. Those are just a few data points. Work with that a bit and see where it gets you. Edited June 3, 2014 by plowmanplow Quote
tchieze Posted June 4, 2014 Author Posted June 4, 2014 Thank you so much! At some point I had to start the server fresh, so I was using a new launch.sh, which set -Xmx3G by default. I changed it to 2G and removed -Xms and today the server held up fine. I don't know how much of a load it had to sustain though, but as of late, it seems better. I'll post if anything else comes up. Thanks again Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.