From 3a71e840e33aa0f303867607ca1ef6756d797316 Mon Sep 17 00:00:00 2001 From: YouHaveTrouble Date: Tue, 29 Dec 2020 02:00:07 +0100 Subject: [PATCH] added performance plugin section, swapped chunky link to github instead of spigot --- README.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 733647a..cefea42 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,7 @@ You shoud stay away from:

Map pregeneration is one of the most important steps to have lag-free server. In modern versions chunk generation is extremely slow and even servers on best -hardware can grind into a halt. You can use plugin such as chunky +hardware can grind into a halt. You can use plugin such as chunky to pregenerate the world. Remember to also set up a world border so your players don't generate new chunks while the server is open to the public! Pregeneration of the map can take hours (it depends on a radius you set in the pregen plugin).

@@ -225,3 +225,19 @@ Hides ores from x-rayers. For detailed configuration of this feature check out

Java startup flags

JVM can be configured to reduce lag spikes caused by big garbage collector tasks. You can find startup flags optimized for minecraft servers here. + +

"Performance" plugins

+ +

Plugins removing ground items

+

+Absolutely unnecessary, can be replaced with spigot configuration +(see merge radius and alt-item-despawn-rate) +and frankly, they're less configurable than basic server configs. The fact that they usually use more resources to scan +and remove items than that items if they would be left alone doesn't help either. +

+ +

Mob stacker plugins

+

+It's really hard to justify using one. Stacking naturally spawned entities causes more lag than not stacking them at all +due to server constantly trying to spawn more mobs. Only "acceptable" use case is spawner mobs on servers with large amount of spawners. +

\ No newline at end of file