Skip to content

Latest commit

 

History

History
37 lines (31 loc) · 2.71 KB

INSTALL.md

File metadata and controls

37 lines (31 loc) · 2.71 KB

Installing TickThreading

  • Install Forge, if you don't already have it. MCPC+ may also be used as the server jar.
  • Download TickThreading
  • Put it in your minecraft mods directory
  • Start the minecraft server, it should close automatically.
  • Run PATCHME.cmd/sh in your minecraft directory
  • Have fun, if anything breaks make an issue report or contact me on EsperNet/Freenode IRC. nick: nallar

Updating TickThreading

  • Remove the old TT jar from your mods folder
  • Add the new jar
  • Start and stop the server OR change the path to the TT jar in the "PATCHME" file
  • Run PATCHME.cmd/sh

Java Tuning

  • Use the latest Java 7.

  • Make sure not to set -Xmx higher than you need - higher values may reduce performance, especially >= 32GB

  • Suggested java parameters - make sure to set -Xmx:
    java -server -XmxG -XX:UseSSE=4 -XX:+UseConcMarkSweepGC -XX:+UseCMSCompactAtFullCollection -XX:+UseParNewGC -XX:+DisableExplicitGC -XX:+AggressiveOpts -jar server.jar nogui

  • Xmx sets the memory the server is allowed to use. It should be set to a reasonable value - enough for the server to run, but not much higher than it needs. >= 32GB will prevent the JVM from using compressed OOPs, an optimisation which reduces the size of pointers and generally gives a reasonable performance boost, so it's a good idea to keep Xmx low.

  • UseConcMarkSweepGC enables the CMS garbage collector. The garbage collector is an important part of the JVM which frees memory used by objects which are no longer needed. By default, a non-concurrent garbage collector is used, which can cause lag spikes if -Xmx is not very small.

  • UseCMSCompactAtFullCollection asks the CMS garbage collector to compact, or defragment, the memory used by the JVM at full collections. When disabled, GC might need to run more often if a large object is allocated which does not fit into any gaps in the heap.

  • UseParNewGC enables concurrent garbage collection for recently created objects, and should be used for the same reasons as for UseConcMarkSweepGC

  • DisableExplicitGC prevents silly mods/plugins from asking the JVM to immediately do a full garbage collection. Otherwise, when a mod/plugin does this, it will always freeze the entire server to perform the garbage collection, ignoring the parameters set above.

  • AggressiveOpts enables experimental JVM options which should improve performance, but may not have been fully tested and could make performance worse in some cases. For example, with the latest Java 7 it enables some optimisations relating to auto boxing - a conversion between primitive and object types.