Direct answer

A newer Java release does not guarantee higher TPS. The required Java major version and supported JVM are determined by the specific Minecraft server version; use that required runtime first, then benchmark.

How to check it

  1. Run java -version using the same Java executable that actually launches the server, not only the default shell Java.
  2. Check the server project’s current Java requirements. For recent Paper releases, the official installation guide documents Java 25; older Minecraft builds may need different Java versions.
  3. Record peak player count, world activity, MSPT, CPU and GC activity with /spark tps and /spark gc. Change no other JVM flags during comparison.
  4. If a runtime change causes a startup error, read the complete stack trace before assuming the server files are damaged.
java -version
/spark tps
/spark gc

What to change

Run each server with an explicit executable path, for example /opt/jdk-25/bin/java on a system where that verified location exists. Test runtime updates on staging with the same plugins. Keep the previously supported runtime available for rollback; never bypass a server software Java compatibility check just to start it.

Software and version notes

Runtime requirements change with Minecraft, Paper, Velocity, mod loaders and builds. Check the official requirement for that exact release rather than using a static Java-version table. Hardware, allocation rate and GC settings often matter more than the major version alone.

Verify the result

Compare comparable busy periods with the same world, player workload and flags. The upgrade is successful only if compatibility is maintained and measured latency or reliability improves.

References