Minecraft Forums

CPU: Dual Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz

RAM: 768GB

Storage: 16TB RAID-10 SSD

OS: VMWare ESXi 6.7

VM Specs:

CPUs: 16

RAM: 32GB

OS: Ubuntu 18.04 LTS

Have 5-6 people on the server and constantly getting:

[20:24:02] [Server thread/WARN]: player123 moved too quickly! 182.2152455613636,3.0,-16.146337543229507 [20:24:17] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2013ms or 40 ticks behind [20:24:38] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2014ms or 40 ticks behind [20:25:31] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2200ms or 44 ticks behind [20:26:12] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2066ms or 41 ticks behind

launch options:

java -Xmx16G -Xms8G -jar server.jar nogui

java version:

openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.18.04.1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)

Any recommendations?

Post the entire server log, use paste.ubuntu.com.

Attempted some additional GC options today, I also allocated all 16G up front as I read this can help.

https://paste.ubuntu.com/p/gsjgbb4z4m/

New launch options:

/usr/bin/java -server -Xms16G -Xmx16G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+AggressiveOpts -XX:+DisableExplicitGC -Xloggc:gc -jar server.jar nogui | tee ~/minecraft_server.log

GC logs: https://paste.ubuntu.com/p/FBNTjZp5Zb/

Attempted a newer version of openjdk on a fresh 18.04 bionic VM. Same specs as above.

Java version:

[root@minecraft ~]# java -version
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.3)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.3, mixed mode)

Startup arguments:

/usr/bin/java -server -Xms16G -Xmx16G -XX:+AggressiveOpts -XX:+DisableExplicitGC -Xlog:gc:gc -jar server.jar nogui

Server log: HERE

This is easiest to duplicate while in a boat exploring new chunks and happens almost immediately.

Yes generating new chunks is very CPU intensive, turn down servers render distance.