This is a comprehensive Paper Minecraft server optimization guide covering configuration tuning for performance.
Key recommendations:
Pre-generate the world map with Chunky/ChunkyBorder before launching your server.
Don't go below
simulation-distance 5,view-distanceshould be ≥simulation-distanceVillagers are uniquely resource-heavy and uncapped by spawn-limits. Use plugins like VillagerLobotomizer or population controls (Available in Purpur by default)
Change
redstone-implementationtoALTERNATE_CURRENT, this will optimize redstone implemenation.
Hardware/JVM guidance
CPU single-core performance matters more than RAM (10GB usually sufficient); MSPT (not TPS) is the real performance metric; modern JVM (21+) handles GC well by default, Aikar's flags or Generational ZGC are optional.
Things to avoid
Mob-stacker plugins, "lag-fix" plugins like ClearLagg/ETF, allowing spawner relocation, datapacks with repeating functions, plugins from untrusted sources, auto-updating Paper builds, anti-Fabric plugins, disabling chat reporting, and over-reliance on anti-cheat plugins.