Neil Hogg
Assigned
Reported
Comments
I upgraded my server to 3 times the amount of ram (had it stupidly set to 2GB of ram on OSX) and ran it with the gui enabled.
I could see that garbage collection was happening frequently and I didn't see the server ever falling behind. Ticks stayed around 3-7 average, but still had some blocks re-appearing, not sure what caused that, as I'm connecting locally while my friends are remote.
My problem was definitely a configuration one and not a fault in the code. Ran the server on both OSX and lubuntu and had no problems.
I went with the server requirements posted on the gamepedia website. It's also notable that these are the requirements just for the server to run and not including OS resources.
Server was sitting idle this morning with no players online. I started debug profiling, and after invoking /seed command got the following logs
[06:59:38] [Server thread/INFO]: Seed: [-8299205347331588351]
[07:01:07] [Server thread/WARN]: Something's taking too long! 'root.tick.save' took aprox 144.547299 ms
[07:01:07] [Server thread/WARN]: Something's taking too long! 'root.tick' took aprox 170.993653 ms
[07:01:07] [Server thread/WARN]: Something's taking too long! 'root' took aprox 171.328691 ms
I then listed players and 3 minutes later, still with no one playing got the same tick warnings.
[07:03:02] [Server thread/INFO]: There are 0 of a max 5 players online:
[07:06:07] [Server thread/WARN]: Something's taking too long! 'root.tick.save' took aprox 124.181894 ms
[07:06:07] [Server thread/WARN]: Something's taking too long! 'root.tick' took aprox 146.617086 ms
[07:06:07] [Server thread/WARN]: Something's taking too long! 'root' took aprox 146.842638 ms
After ending debug server indicated 20,00 ticks per second. See attached logs
[07:06:47] [Server thread/INFO]: Stopped debug profiling after 578.45 seconds and 11570 ticks (20,00 ticks per second)
Experiencing the same on 1.14.1. My server would just sit idle and then start throwing
Can't keep up! Is the server overloaded? Running 2407ms or 48 ticks behind
It's currently unplayable. Have to restart the server every 5 minutes if we're more than 1 playing, and it doesn't help increasing ram constraints.
@Christopher Martin
I had to up the ram to 4GB for the server to just idle without getting behind on ticks. I saw on the GUI that the ram built up to around 3GB+ almost 4GB before garbage collection was invoked, this obviously happens way quicker when someone is playing. We are 3 players on the server and with 6GB of ram we could play relatively stable, other than the issues I mentioned before. I saw no issue with cpu performance (running on a 2013 iMac) so I don't think the issue is with processing although others have mentioned their CPU running at 100%. My biggest issue was RAM, and I'm guessing there's a very inefficient piece of code somewhere that causes the ram to build up to that point before java vm decides to do cleanup.
The Server Requirements I linked above do say that the server should be able to handle 1 user on 512MB of RAM but in my experience with 1.14, 1.14.1 and 1.14.2 pre release that, that is impossible.
—
UPDATE - The high amount of ram on idle because of garbage collection was my mistake. Setting the Xms Java Virtual Machine constraint to a lower value improved garbage collection drastically when the server is on idle but that makes total sense.