Benchmark Report
Personal computer server of mine, this is not a host.
Tick spikes · Mob AI
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 128.5 ms
- mspt_p99 = 562.5 ms
- spike_ratio = 4.38 ratio
- sample_count = 124 count
Weakest test: Mob AI, 9.11 TPS on average. The 15 other tests hold at least 19.48 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 estimatedTick spikes
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 128.5 ms
- mspt_p99 = 562.5 ms
- spike_ratio = 4.38 ratio
- sample_count = 124 count
Tick spikes
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 23.6 ms
- mspt_p99 = 50.78 ms
- spike_ratio = 2.15 ratio
- sample_count = 96 count
›+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- Mob AIEntities9.11UnstableCritical
- Network (NBT)Network19.97ModerateUnstable
- Multi-Core CPUCPU19.48StableHealthy
- Chunk LoadingExploration19.92UnstableHealthy
- HopperMechanics19.95StableHealthy
- Bone Meal GrowthMechanics19.96StableHealthy
- Lighting UpdateExploration19.96ModerateHealthy
- Ticking Tile EntitiesMechanics19.96StableHealthy
- Block PhysicsSingle-Core Stress19.97ModerateHealthy
- Chunk TickingExploration19.97StableHealthy
- Disk PerformanceMemory & Storage19.97StableHealthy
- ExplosionMechanics19.97StableHealthy
- Memory PerformanceMemory & Storage19.97StableHealthy
- RedstoneSingle-Core Stress19.97UnstableHealthy
- Single-Core (tick-aligned)CPU19.97StableHealthy
- 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.
Shrink the monster activation range
world-settings.default.entity-activation-range.monsters: 24Measured : mobAI.mspt.avg 128.5 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: 50Measured : mobAI.mspt.avg 128.5 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": "purpur",
"minecraft": "1.21.11",
"java": "21.0.10"
},
"recommendations": [
{
"id": "spigot.portee-activation-monstres",
"family": "spigot",
"measure": "mobAI.mspt.avg",
"value": 128.5,
"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": 128.5,
"unit": "ms",
"threshold": 50,
"control_test": "mobAI",
"file": "bukkit.yml",
"setting": "spawn-limits.monsters",
"proposed_value": "50",
"current_value": null
}
]
}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 (23 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-Xms6144M -Xmx6144M --add-modules=jdk.incubator.vector -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:ParallelGCThreads=8 -XX:ConcGCThreads=2
Nothing to correct: every option is valid for Java 21.
Re-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
RedstoneHealthy19.97 TPS27.9 ms32.0s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection20 collections, 79ms total
Percentiles and stability
Raw data (3 fields)
Block PhysicsHealthy19.97 TPS14.8 ms20.1s
Single-core stress via falling-block physics.
Percentiles and stability
Raw data (2 fields)
Exploration
Chunk LoadingHealthy19.92 TPS5.5 ms6.8s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection2 collections, 181ms total
Percentiles and stability
Raw data (2 fields)
Chunk TickingHealthy19.97 TPS14.9 ms40.9s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection6 collections, 83ms total
Percentiles and stability
Raw data (3 fields)
Lighting UpdateHealthy19.96 TPS2.7 ms24.6s
Lighting recomputation throughput on block place / break.
Percentiles and stability
Entities
Mob AICritical9.11 TPS128.5 ms27.5s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Unfiltered samples usedUsing unfiltered samples (filter rate: 90%)
- Heavy garbage collection9 collections, 246ms total
- The run did not hold steadyTPS avg=9,11<19, TPS P1=4,96<15, TPS StdDev=3,78>2, TPS min=4,96 (54% of avg)
Percentiles and stability
Raw data (12 fields)
Mechanics
HopperHealthy19.95 TPS1.3 ms19.0s
Intensive hopper chain item transfers.
Percentiles and stability
ExplosionHealthy19.97 TPS3.2 ms17.0s
Massive TNT explosions and block destruction.
Percentiles and stability
Ticking Tile EntitiesHealthy19.96 TPS1.7 ms36.1s
Many ticking tile entities (furnaces, hoppers, etc.).
- Heavy garbage collection3 collections, 17ms total
Percentiles and stability
Raw data (2 fields)
World SaveHealthy19.98 TPS0.4 ms5.0s
World save speed and TPS impact during save operations.
Percentiles and stability
Bone Meal GrowthHealthy19.96 TPS1.4 ms22.0s
Rapid crop and tree growth via bone meal.
Percentiles and stability
Raw data (6 fields)
CPU
Single-Core (tick-aligned)Healthy19.97 TPS2.9 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
Percentiles and stability
Raw data (1 field)
Multi-Core CPUHealthy19.48 TPS2.0 ms3.2s
Parallel computation throughput across worker threads.
Percentiles and stability
Raw data (1 field)
Memory & Storage
Memory PerformanceHealthy19.97 TPS2.0 ms55.6s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
Percentiles and stability
Disk PerformanceHealthy19.97 TPS2.2 ms90.5s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection6 collections, 40ms total
Percentiles and stability
Raw data (3 fields)
Network
Network (NBT)Unstable19.97 TPS23.6 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection9 collections, 41ms total
Percentiles and stability
Raw data (2 fields)
›Machine and serverGenuine Intel(R) 0000 · Purpur · 1.21.11
Score Breakdown
Detailed sub-category scores