Here are parameters for the server to test if it works for more performance:
-server -d64 -Xrs -Xmx350m -XX:ThreadPriorityPolicy=42 -XX:+TieredCompilation -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=15 -XX:+UnlockExperimentalVMOptions -XX:+UseBiasedLocking -XX:UseSSE=4 -XX:+UseCodeCacheFlushing -XX:+UseThreadPriorities -XX:+UseFastAccessorMethods -XX:+AggressiveOpts -XX:+ReduceSignalUsage -XX:+UseInterpreter -XX:+UseFastEmptyMethods -XX:+UseSharedSpaces -XX:AllocatePrefetchStyle=1 -XX:+AlwaysCompileLoopMethods -XX:SharedReadOnlySize=30m -XX:+UseConcMarkSweepGC -XX:+RewriteFrequentPairs -XX:+CMSCleanOnEnter -XX:+UseSplitVerifier -XX:+UseInlineCaches
That -Xmx350m, ahh… change it if you like.
Download JDK here for it to work – it includes the server runtime for higher performance – and pick the 64 and 32-bit version:
https://jdk7.java.net/download.html
It seems risky. Try to make another private server and test if it works.
If it works, try to apply it to the whole server.
You may remove the -d64 thing to make -xmx work if you see that the server is not working properly.
Glad to help you!
Not forcing, just a suggestion.
Sorry, the comment form is closed at this time.