Benchmark Report
Main thread saturated · Redstone
One game thread is already over its tick budget under the benchmark's own load. Players and redstone will push it further.
- mspt_avg = 56.7 ms
- mspt_target = 35 ms
- tps_avg = 16.75 tps
- tps_held_threshold = 18 tps
Weakest test: Mob AI, 5.8 TPS on average. The 15 other tests hold at least 16.75 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 estimatedMain thread saturated
One game thread is already over its tick budget under the benchmark's own load. Players and redstone will push it further.
Likely cause: single core
- mspt_avg = 56.7 ms
- mspt_target = 35 ms
- tps_avg = 16.75 tps
- tps_held_threshold = 18 tps
Tick spikes
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 254.6 ms
- mspt_p99 = 1,171.88 ms
- spike_ratio = 4.6 ratio
- sample_count = 97 count
Non-default server configuration
Compare with care against a server running default settings.
- spawn-limit.water-ambient 15 (default 20)
›+3 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
redstoneThe worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 56.7 ms
- mspt_p99 = 296.88 ms
- spike_ratio = 5.24 ratio
- sample_count = 77 count
- periodic_test = 1
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- Mob AIEntities5.80UnstableCritical
- RedstoneSingle-Core Stress16.75UnstableCritical
- Multi-Core CPUCPU19.60StableHealthy
- Block PhysicsSingle-Core Stress19.91UnstableHealthy
- Chunk LoadingExploration19.93ModerateHealthy
- Network (NBT)Network19.93ModerateHealthy
- HopperMechanics19.95StableHealthy
- Bone Meal GrowthMechanics19.98StableHealthy
- Chunk TickingExploration19.98ModerateHealthy
- Disk PerformanceMemory & Storage19.98StableHealthy
- ExplosionMechanics19.98ModerateHealthy
- Lighting UpdateExploration19.98StableHealthy
- Memory PerformanceMemory & Storage19.98StableHealthy
- Single-Core (tick-aligned)CPU19.98StableHealthy
- Ticking Tile EntitiesMechanics19.98StableHealthy
- World SaveMechanics19.98StableHealthy
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.
Switch the redstone implementation
misc.redstone-implementation: ALTERNATE_CURRENTMeasured : redstone.mspt.avg 56.7 ms (threshold 35.0 ms)
Redstone costs more per tick than the budget allows. Paper ships an alternative wire implementation that computes the same result without the repeated updates of the vanilla one.
Test to replay : redstone
Shrink the monster activation range
world-settings.default.entity-activation-range.monsters: 24Measured : mobAI.mspt.avg 254.6 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
Lower the monster spawn limit
spawn-limits.monsters: 50Currently : 70
Measured : mobAI.mspt.avg 254.6 ms (threshold 50.0 ms)
Mob AI is past the critical cost per tick, where shrinking the activation range is no longer enough. The spawn limit caps how many monsters exist per player at all, which is the only setting here that reduces the work rather than deferring it.
Test to replay : mobAI
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": "paper",
"minecraft": "1.21.11",
"java": "21.0.12"
},
"recommendations": [
{
"id": "paper.redstone-alternatif",
"family": "paper",
"measure": "redstone.mspt.avg",
"value": 56.7,
"unit": "ms",
"threshold": 35,
"control_test": "redstone",
"file": "config/paper-world-defaults.yml",
"setting": "misc.redstone-implementation",
"proposed_value": "ALTERNATE_CURRENT",
"current_value": null
},
{
"id": "spigot.portee-activation-monstres",
"family": "spigot",
"measure": "mobAI.mspt.avg",
"value": 254.6,
"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": "bukkit.limite-monstres",
"family": "bukkit",
"measure": "mobAI.mspt.avg",
"value": 254.6,
"unit": "ms",
"threshold": 50,
"control_test": "mobAI",
"file": "bukkit.yml",
"setting": "spawn-limits.monsters",
"proposed_value": "50",
"current_value": "70"
}
]
}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 (7 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-Xms8G -Xmx16G -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:+ParallelRefProcEnabled -XX:+PerfDisableSharedMem -Dfile.encoding=UTF-8
Nothing to correct: every option is valid for Java 21.
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.
-Xms16384M -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: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. On Java 21 and 22 the generational mode needs -XX:+ZGenerational.
-XX:+UseZGC -XX:+ZGenerationalNo 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
RedstoneCritical16.75 TPS56.7 ms34.3s
Single-core stress via intensive redstone circuit updates.
- Unfiltered samples usedUsing unfiltered samples (filter rate: 75%)
- Heavy garbage collection9 collections, 670ms total
- The run did not hold steadyTPS avg=16,75<19, TPS P1=4,99<15, TPS StdDev=11,29>2, TPS min=4,99 (30% of avg)
Percentiles and stability
Raw data (4 fields)
Block PhysicsHealthy19.91 TPS24.9 ms20.5s
Single-core stress via falling-block physics.
- Heavy garbage collection3 collections, 502ms total
Percentiles and stability
Raw data (5 fields)
Exploration
Chunk LoadingHealthy19.93 TPS4.3 ms12.8s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection3 collections, 1420ms total
Percentiles and stability
Raw data (2 fields)
Chunk TickingHealthy19.98 TPS22.6 ms41.3s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection4 collections, 640ms total
Percentiles and stability
Raw data (3 fields)
Lighting UpdateHealthy19.98 TPS3.0 ms24.8s
Lighting recomputation throughput on block place / break.
- Heavy garbage collection1 collections, 152ms total
Percentiles and stability
Raw data (2 fields)
Entities
Mob AICritical5.80 TPS254.6 ms28.2s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Unfiltered samples usedUsing unfiltered samples (filter rate: 96%)
- Heavy garbage collection2 collections, 313ms total
- The run did not hold steadyTPS avg=5,80<19, TPS P1=2,94<15, TPS StdDev=3,13>2, TPS min=2,94 (51% of avg)
Percentiles and stability
Raw data (12 fields)
Mechanics
HopperHealthy19.95 TPS3.1 ms19.1s
Intensive hopper chain item transfers.
- Heavy garbage collection3 collections, 537ms total
Percentiles and stability
Raw data (2 fields)
ExplosionHealthy19.98 TPS4.4 ms17.4s
Massive TNT explosions and block destruction.
- Heavy garbage collection3 collections, 617ms total
Percentiles and stability
Raw data (2 fields)
Ticking Tile EntitiesHealthy19.98 TPS2.6 ms36.6s
Many ticking tile entities (furnaces, hoppers, etc.).
- Heavy garbage collection3 collections, 556ms total
Percentiles and stability
Raw data (2 fields)
World SaveHealthy19.98 TPS2.9 ms4.9s
World save speed and TPS impact during save operations.
- Heavy garbage collection3 collections, 464ms total
Percentiles and stability
Raw data (2 fields)
Bone Meal GrowthHealthy19.98 TPS2.7 ms22.1s
Rapid crop and tree growth via bone meal.
- Heavy garbage collection1 collections, 180ms total
Percentiles and stability
Raw data (8 fields)
CPU
Single-Core (tick-aligned)Healthy19.98 TPS3.1 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
- Heavy garbage collection3 collections, 458ms total
Percentiles and stability
Raw data (4 fields)
Multi-Core CPUHealthy19.60 TPS2.2 ms31.7s
Parallel computation throughput across worker threads.
- Heavy garbage collection1 collections, 151ms total
Percentiles and stability
Raw data (4 fields)
Memory & Storage
Memory PerformanceHealthy19.98 TPS2.7 ms85.2s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection4 collections, 555ms total
Percentiles and stability
Raw data (2 fields)
Disk PerformanceHealthy19.98 TPS3.1 ms110.5s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection4 collections, 238ms total
Percentiles and stability
Raw data (3 fields)
Network
Network (NBT)Healthy19.93 TPS46.0 ms20.4s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection4 collections, 166ms total
Percentiles and stability
Raw data (2 fields)
›Machine and serverIntel(R) Core(TM) i7-4790K CPU @ 4.00GHz · Paper · 1.21.11
Score Breakdown
Detailed sub-category scores