Benchmark Report
Nothing crossed a threshold
No measurement of this run points to a defect. That describes this run under this load, not every load.
Weakest test: Chunk Loading, 3.45 TPS on average. The 15 other tests hold at least 7.79 TPS.
Compared with other servers
The comparison with other servers uses reports scored with version 8.3.0 of the scoring rules. This report was scored with another version, so its score is not comparable.
What matters
Read from the measurements, never estimatedNon-default server configuration
Compare with care against a server running default settings.
- view-distance 12 (default 10)
- simulation-distance 5 (default 10)
- spawn-limit.monster 20 (default 70)
+5 more modified settings
›+2 more findings
memorynot measuredNo access latency was published, so the score assumed an unfavourable one. Publishing the measurement can only help.
- assumed_latency_ns = 180 ns
- reference_latency_ns = 120 ns
disknot measuredDirect IO was refused by the host, so the random part of the disk score rests on an assumption rather than a measurement.
- assumed_random_mbps = 90 MB/s
- reference_random_mbps = 150 MB/s
A finding stays silent rather than attribute a cause without evidence. An absent cause is an answer, not an omission.
Test by test
Problems first — select a row for the full test- Chunk LoadingExploration3.45StableUnstable
- Mob AIEntities7.79StableUnstable
- Bone Meal GrowthMechanics13.18StableUnstable
- ExplosionMechanics14.59StableUnstable
- Block PhysicsSingle-Core Stress19.93StableHealthy
- Multi-Core CPUCPU19.97StableHealthy
- Chunk TickingExploration20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- HopperMechanics20.00StableHealthy
- Lighting UpdateExploration20.00UnstableHealthy
- Memory PerformanceMemory & Storage20.00StableHealthy
- Network (NBT)Network20.00ModerateHealthy
- RedstoneSingle-Core Stress20.00StableHealthy
- Single-Core (tick-aligned)CPU20.00StableHealthy
- Ticking Tile EntitiesMechanics20.00StableHealthy
- World SaveMechanics20.00StableHealthy
Settings your measurements justify
Each setting below is triggered by a measurement from this report, and names the test to replay to find out whether it helped.
Shrink the monster activation range
world-settings.default.entity-activation-range.monsters: 24Measured : mobAI.mspt.avg 128.3 ms (threshold 35.0 ms)
Mob AI costs more per tick than the budget allows. The activation range decides how far from a player a monster keeps thinking; shrinking it puts distant ones to sleep without removing them.
Test to replay : mobAI
Cap the TNT processed per tick
world-settings.default.max-tnt-per-tick: 40Measured : explosion.mspt.avg 75.6 ms (threshold 35.0 ms)
Explosions cost more per tick than the budget allows. Capping how many primed entities are processed per tick spreads a large blast over several ticks instead of one long freeze.
Test to replay : explosion
Lower the simulation distance
simulation-distance: 4Currently : 5
Measured : chunkTicking.mspt.avg 50.0 ms (threshold 50.0 ms)
Chunk ticking is past the critical cost per tick. The simulation distance decides how many chunks tick around each player; lowering it a notch is the bluntest lever here and the one players notice, so it is offered only when the value in use is known.
Test to replay : chunkTicking
These settings trade a little gameplay fidelity for tick budget. Apply one at a time and replay the named test: the effect stays a hypothesis until you have measured it.
Briefing for a language model
Paste this into the assistant of your choice to have it rewritten in prose. It already carries every number, so the model has none left to invent.
{
"format": "voxelbench.tuning.v1",
"instruction": "Rewrite each recommendation below as plain prose for a server operator. Every number you are allowed to use is already in this document: the measured value, its threshold, and the proposed setting. Do not compute, estimate or predict any other number, and never state an expected gain. Keep every setting name and value exactly as written.",
"server": {
"type": "folia",
"minecraft": "26.1.2",
"java": "25.0.2"
},
"recommendations": [
{
"id": "spigot.portee-activation-monstres",
"family": "spigot",
"measure": "mobAI.mspt.avg",
"value": 128.3,
"unit": "ms",
"threshold": 35,
"control_test": "mobAI",
"file": "spigot.yml",
"setting": "world-settings.default.entity-activation-range.monsters",
"proposed_value": "24",
"current_value": null
},
{
"id": "spigot.tnt-par-tick",
"family": "spigot",
"measure": "explosion.mspt.avg",
"value": 75.6,
"unit": "ms",
"threshold": 35,
"control_test": "explosion",
"file": "spigot.yml",
"setting": "world-settings.default.max-tnt-per-tick",
"proposed_value": "40",
"current_value": null
},
{
"id": "serveur.distance-de-simulation",
"family": "serveur",
"measure": "chunkTicking.mspt.avg",
"value": 50,
"unit": "ms",
"threshold": 50,
"control_test": "chunkTicking",
"file": "server.properties",
"setting": "simulation-distance",
"proposed_value": "4",
"current_value": "5"
}
]
}Java start-up line
The options this server was started with, checked against its Java version. Corrections fix what is certainly wrong; leads to test are settings to measure, never applied for you.
Current line (8 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-XX:ThreadPriorityPolicy=1 -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCIProduct -XX:+EnableJVMCI -XX:-UnlockExperimentalVMOptions -Xms16G -Xmx32G --add-modules=jdk.incubator.vector
To correct
- To correctOption set more than once
-XX:-UnlockExperimentalVMOptionsThe JVM keeps only the last occurrence (-XX:-UnlockExperimentalVMOptions); the earlier ones do nothing but mislead whoever reads the line.
Corrected line to copy
- Removed
-XX:+UnlockExperimentalVMOptionsearlier occurrence; the JVM keeps -XX:-UnlockExperimentalVMOptions.
java -XX:ThreadPriorityPolicy=1 -XX:+EnableJVMCIProduct -XX:+EnableJVMCI -XX:-UnlockExperimentalVMOptions -Xms16G -Xmx32G -jar server.jar noguiReplace server.jar with your server's jar. Paste the line where your server is started: the start-up parameters (or JVM arguments) of your hosting panel, or your start.sh / start.bat. Only the corrections above differ from your current line.
Your current line also carries 1 other argument (system properties, agents): keep them between java and -jar. Their values are not shown here.
To test
Performance settings to try one at a time, then measure with a benchmark before and after. None of them is applied in the corrected line, and none comes with a promised gain.
Settings documented by PaperMC for Minecraft servers: they size G1's young generation for the game's very high allocation rate and start collections earlier. Initial and maximum heap at the same size, with AlwaysPreTouch, commit the whole heap at start-up: proposed only because that heap already stays under the memory limit.
-Xms32768M -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1No measurement of this run points to it: it stays a lead to measure.
sourceA collector with very short pauses for large heaps, at the cost of more CPU and memory. It replaces the current collector: remove the current collector option and its own tuning options, then measure. From Java 23 the generational mode is the default.
-XX:+UseZGCNo measurement of this run points to it: it stays a lead to measure.
sourceRe-run and compare
- Apply the corrected line where your server starts (panel start-up parameters, start.sh).
- Restart the server.
- Run a new benchmark:
/bench start - Compare the new report with this one.
This report is the before; add the new report to the comparison once it is in. A single run on each side says little: the gap between two runs of an unchanged server is noise.
Every measurement
Each test in full. Tests in trouble are open; the others fold to their summary line.
Single-Core Stress
RedstoneHealthy20.00 TPS0.3 ms34.0s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection7 collections, 746ms total
Percentiles and stability
Raw data (3 fields)
Block PhysicsHealthy19.93 TPS0.2 ms21.9s
Single-core stress via falling-block physics.
- Heavy garbage collection4 collections, 707ms total
Percentiles and stability
Raw data (5 fields)
Exploration
Chunk LoadingUnstable3.45 TPS290.2 ms8.4s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection2 collections, 1009ms total
- The run did not hold steadyTPS avg=3.45<19
Percentiles and stability
Raw data (2 fields)
Chunk TickingHealthy20.00 TPS50.0 ms36.5s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection3 collections, 581ms total
Percentiles and stability
Raw data (3 fields)
Lighting UpdateHealthy20.00 TPS50.0 ms9.7s
Lighting recomputation throughput on block place / break.
- Heavy garbage collection1 collections, 173ms total
Percentiles and stability
Raw data (2 fields)
Entities
Mob AIUnstable7.79 TPS128.3 ms28.4s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Heavy garbage collection6 collections, 356ms total
- The run did not hold steadyTPS avg=7.79<19
Percentiles and stability
Raw data (11 fields)
Mechanics
HopperHealthy20.00 TPS50.0 ms23.2s
Intensive hopper chain item transfers.
- Heavy garbage collection19 collections, 9507ms total
Percentiles and stability
Raw data (2 fields)
ExplosionUnstable14.59 TPS75.6 ms7.0s
Massive TNT explosions and block destruction.
- Heavy garbage collection3 collections, 487ms total
- The run did not hold steadyTPS avg=14.59<19, TPS min=10.14 (69% of avg)
Percentiles and stability
Raw data (2 fields)
Ticking Tile EntitiesHealthy20.00 TPS50.0 ms37.2s
Many ticking tile entities (furnaces, hoppers, etc.).
- Heavy garbage collection4 collections, 725ms total
Percentiles and stability
Raw data (2 fields)
World SaveHealthy20.00 TPS50.0 ms4.9s
World save speed and TPS impact during save operations.
- Heavy garbage collection3 collections, 540ms total
Percentiles and stability
Raw data (2 fields)
Bone Meal GrowthUnstable13.18 TPS75.9 ms22.4s
Rapid crop and tree growth via bone meal.
- Heavy garbage collection1 collections, 238ms total
- The run did not hold steadyTPS avg=13.18<19
Percentiles and stability
Raw data (8 fields)
CPU
Single-Core (tick-aligned)Healthy20.00 TPS1.3 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
- Heavy garbage collection4 collections, 705ms total
Percentiles and stability
Raw data (4 fields)
Multi-Core CPUHealthy19.97 TPS0.3 ms5.9s
Parallel computation throughput across worker threads.
- Heavy garbage collection1 collections, 163ms total
Percentiles and stability
Raw data (4 fields)
Memory & Storage
Memory PerformanceHealthy20.00 TPS0.3 ms61.9s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection4 collections, 658ms total
Percentiles and stability
Raw data (2 fields)
Disk PerformanceHealthy20.00 TPS0.3 ms34.4s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection2 collections, 338ms total
Percentiles and stability
Raw data (3 fields)
Network
Network (NBT)Healthy20.00 TPS21.2 ms20.1s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection3 collections, 189ms total
Percentiles and stability
Raw data (2 fields)
›Machine and serverAMD Ryzen 9 9950X 16-Core Processor · Folia · 26.1.2
Score Breakdown
Detailed sub-category scores