Minecraft Server Performance Audit Guide
Run a Minecraft server performance audit covering TPS, MSPT, Spark profiles, plugins, entities, chunks, configs, JVM flags, backups, and capacity limits.
A performance audit is a structured review of how your Minecraft server behaves under real load. It keeps you from guessing.
Audit Inputs
Collect:
| Input | Why it matters | | --- | --- | | TPS and MSPT | Main performance health | | Spark profile | Shows where tick time goes | | Plugin list | Finds risky features and dependencies | | server.properties | View distance and simulation distance | | Paper/Spigot/Purpur configs | Entity, chunk, and behavior controls | | World notes | Farms, villagers, borders, resource worlds | | Hardware info | CPU, RAM, storage, host type |
Step 1: Baseline
Record normal peak player count, average MSPT, worst spikes, and the time lag usually happens. Do not tune from an empty-server profile.
Use Spark during the problem window.
Step 2: Classify the Bottleneck
| Profile points to | Next action | | --- | --- | | Plugins | Find laggy plugins | | Entities | Entity lag | | Chunks | Chunk lag | | Hoppers | Optimize hoppers | | Villagers | Optimize villagers | | CPU | High CPU fix |
Step 3: Review Settings
Check:
- View distance.
- Simulation distance.
- Mob spawn limits.
- Entity activation ranges.
- Hopper behavior.
- Backup schedule.
- Plugin update intervals.
Use the server.properties generator and JVM flag generator for baseline comparisons.
Step 4: Produce an Action List
Separate actions into:
- Immediate safe changes.
- Changes needing player notice.
- Staging-only tests.
- Host or hardware decisions.
- Long-term server rules.
An audit is successful when it produces fewer guesses and clearer priorities.
FAQ
When should I run a performance audit?
Run one before launch, after major plugin changes, before increasing slots, and whenever recurring lag appears.
How long does an audit take?
A useful first audit can take 30 to 60 minutes, but deeper plugin or world investigations may take longer.
Should I change settings during the audit?
Collect baseline evidence first. Then change one area at a time and compare results.
Related Tools
Startup Log Classifier
Paste a Minecraft startup log excerpt to classify Java mismatch, port conflicts, memory errors, plugin failures, dependency issues, and TPS overload.
Plugin Conflict Auditor
Paste a Minecraft plugin list to flag common dependency, compatibility, ProtocolLib, LuckPerms, ViaVersion, and proxy risk areas.
Minecraft JVM Flag Generator
Generate practical Minecraft server JVM flags for Paper, Purpur, Forge, Fabric, and Velocity with sensible heap sizing and GC reminders.
Related Articles
Minecraft Server Lag Checklist
Use this Minecraft server lag checklist to triage TPS drops, plugins, entities, chunks, hoppers, villagers, CPU, RAM, backups, and player reports.
How to Use Spark Profiler on Minecraft Server
Use Spark profiler on a Minecraft server to capture TPS lag, read MSPT clues, avoid idle profiles, and turn profiler reports into focused fixes.
Common Causes of Minecraft Server Lag
Diagnose common Minecraft server lag causes including entities, chunks, plugins, redstone, hoppers, villagers, CPU limits, storage stalls, and RAM myths.