
HeavenCube Benchmark
Rapport fait le software: "26.3-223-main@e415f5e".
Tick spikes · Mob AI
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 237.4 ms
- mspt_p99 = 563.8 ms
- spike_ratio = 2.37 ratio
- sample_count = 96 count
- spike_ticks = 2 count
- spike_window_ticks = 108 count
- spike_threshold_ms = 452.4 ms
- spike_ticks_with_gc = 0 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 2,301.1 ms
- spike_gc_pause_ms = 0 ms
- spike_throttled_ms = 0 ms
- spike_sample_interval_ms = 40 ms
- explained_share_threshold = 0.5 ratio
- explained_time_share_threshold = 0.25 ratio
Weakest test: Mob AI, 5.21 TPS on average. The 15 other tests hold at least 19.85 TPS.
Compared with other servers
Every measured server counts here, including private, anonymous and expired reports. Each server counts once, with its best run.
This report scores better than
81%
of the 9 servers running Paper & forks
Total score 102,703 · group median 85,678
Top quarter- Single Core
Better than 76% · 143,296 vs median 104,683 · Top quarter
- Gameplay
Better than 56% · 62,251 vs median 61,803
- Exploration
Better than 65% · 83,587 vs median 79,594
- Entities
Better than 40% · 63,636 vs median 68,912
- Mechanics
Better than 43% · 46,226 vs median 46,275
- Hardware
Better than 87% · 48,630 vs median 36,588 · Top quarter
- Memory
Better than 10% · 19,551 vs median 21,046 · Bottom quarter
- Disk
Better than 88% · 79,235 vs median 44,420 · Top quarter
- Multi-Core
Better than 74% · 76,898 vs median 67,413
Test by test
Each tick test's average MSPT (lower is better) and TPS, against the same group, each server with the same run as above. A test shows when at least 5 servers of the group passed it. The bar follows the MSPT.
- Block Physics
Better than 34% · MSPT 17.7 ms vs median 15.5 ms · TPS 19.9 vs median 20
- Bone Meal Growth
Better than 24% · MSPT 2.6 ms vs median 2.1 ms · TPS 20 vs median 20 · Bottom quarter
- Chunk Loading
Better than 30% · MSPT 7.1 ms vs median 4.8 ms · TPS 19.9 vs median 19.5
- Chunk Ticking
Better than 24% · MSPT 25 ms vs median 18.4 ms · TPS 20 vs median 20 · Bottom quarter
- Explosion
Better than 33% · MSPT 5.8 ms vs median 5 ms · TPS 20 vs median 19.9
- Hopper
Better than 50% · MSPT 3 ms vs median 3 ms · TPS 20 vs median 19.9
- Lighting Update
Better than 22% · MSPT 3.4 ms vs median 2.4 ms · TPS 20 vs median 20 · Bottom quarter
- Mob AI
Better than 39% · MSPT 237.4 ms vs median 180.4 ms · TPS 5.2 vs median 6.8
- Redstone
Better than 88% · MSPT 13.4 ms vs median 24.7 ms · TPS 20 vs median 18.3 · Top quarter
- Ticking Tile Entities
Better than 40% · MSPT 5.6 ms vs median 4.4 ms · TPS 20 vs median 20
- World Save
Better than 24% · MSPT 2.3 ms vs median 1.8 ms · TPS 20 vs median 20 · Bottom quarter
Scored with version 8.3.0 of the scoring rules. Groups of fewer than 5 servers are never used. Updated Oct 26, 2026, 6:40 PM UTC. Community trends · All measurements by CPU
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 = 237.4 ms
- mspt_p99 = 563.8 ms
- spike_ratio = 2.37 ratio
- sample_count = 96 count
- spike_ticks = 2 count
- spike_window_ticks = 108 count
- spike_threshold_ms = 452.4 ms
- spike_ticks_with_gc = 0 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 2,301.1 ms
- spike_gc_pause_ms = 0 ms
- spike_throttled_ms = 0 ms
- spike_sample_interval_ms = 40 ms
- explained_share_threshold = 0.5 ratio
- explained_time_share_threshold = 0.25 ratio
Non-default server configuration
Compare with care against a server running default settings.
- view-distance 6 (default 10)
- simulation-distance 6 (default 10)
- spigot:mob-spawn-range 5 (default 8)
+4 more modified settings
CPU quota
The JVM sees far fewer cores than the host advertises. Everything that parallelises is bounded by the container, not by the machine.
Likely cause: CPU quota
- host_threads = 24 cores
- usable_cores = 8 cores
- core_ratio = 3 ratio
›+2 more findings
networkThe worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 25.6 ms
- mspt_p99 = 100.31 ms
- spike_ratio = 3.92 ratio
- sample_count = 98 count
- spike_ticks = 3 count
- spike_window_ticks = 420 count
- spike_threshold_ms = 50 ms
- spike_ticks_with_gc = 0 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 665.7 ms
- spike_gc_pause_ms = 0 ms
- spike_throttled_ms = 0 ms
- spike_sample_interval_ms = 40 ms
- explained_share_threshold = 0.5 ratio
- explained_time_share_threshold = 0.25 ratio
The run started on a JVM that had just started, or that had not run a bench since it started: code was still being compiled and the heap still growing. The first run after a restart can differ from the next ones.
- jvm_uptime_s = 58 s
- bench_runs_since_start = 0 count
- threshold_s = 300 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 AIEntities5.21UnstableCritical
- Network (NBT)Network19.85UnstableUnstable
- Block PhysicsSingle-Core Stress19.86ModerateUnstable
- Chunk LoadingExploration19.90UnstableUnstable
- Ticking Tile EntitiesMechanics19.96StableHealthy
- HopperMechanics19.98StableHealthy
- Memory PerformanceMemory & Storage19.99StableHealthy
- Multi-Core CPUCPU19.99StableHealthy
- Bone Meal GrowthMechanics20.00StableHealthy
- Chunk TickingExploration20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- ExplosionMechanics20.00StableHealthy
- Lighting UpdateExploration20.00StableHealthy
- RedstoneSingle-Core Stress20.00effective 20.0StableHealthy
- Single-Core (tick-aligned)CPU20.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 237.4 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 237.4 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": "26.3",
"java": "25.0.3"
},
"recommendations": [
{
"id": "spigot.portee-activation-monstres",
"family": "spigot",
"measure": "mobAI.mspt.avg",
"value": 237.4,
"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": 237.4,
"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 (20 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-Xms10240M -Xmx10240M --add-modules=jdk.incubator.vector -XX:+UseCompactObjectHeaders -XX:+PerfDisableSharedMem -XX:+UseZGC -XX:-ZProactive -XX:ZAllocationSpikeTolerance=3 -XX:ReservedCodeCacheSize=512M -XX:InitialCodeCacheSize=32M -XX:CompileThresholdScaling=0.75 -XX:+UseThreadPriorities -XX:+AlwaysPreTouch -Duser.timezone=Europe/Paris -Dnet.kyori.ansi.colorLevel=<redacted> -Dfile.encoding=UTF-8 --sun-misc-unsafe-memory-access=allow -Xlog:async -Dterminal.jline=false -Dterminal.ansi=true
Nothing to correct: every option is valid for Java 25.
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.
Run conditions
What the plugin saw of the host during the benchmark, and what the site concludes from it. The plugin reports facts; the verdicts and their thresholds are the site's, the same ones the diagnosis and the API use.
The reference computation timed during the run kept its pace, and the hypervisor took no significant CPU time.
A CPU quota, a reduced CPU set or a memory limit applies to the server.
Contention during the run
- Reference computation slowdown
- 1.3 % (threshold 15 %)3 timings: 13.2 ms · 13.2 ms · 13 ms (a slow first timing alone does not count) — judged on the median of at least 40 samples per timing (plugin 2.6.2); host noise 4.1 %, the threshold widens to it, from 15 to 30 % — wait for the server to settle before Hopper, after chunk loading: 0.0 s (limit 30.0 s, after chunk generation) · longest wait, before Block Physics: 1.9 s (limit 8.0 s, default limit)
- CPU time stolen by the hypervisor
- 0 % (threshold 5 %)
- Scheduling periods ended throttled by the quota
- 1.9 % (threshold 25 %)5,645.8 ms
- Time a task waited for a core
- 0.2 % (threshold 40 %)
Limits seen by the server
- CPU quota
- 7.5 cores
- CPU set
- 0-23 (24 cores)
- Memory limit
- 24 GiB
- Host logical CPUs
- 24
- Host memory
- 186.4 GiB
- Container signals
- dockerenv, cgroup-v2-namespace, overlay-root, pterodactyl-env
Storage
- Filesystem
- ext4 · Local filesystem
- Direct 4K reads
- Honoured (48.9 µs against 0.5 µs from cache)
Single-core measurement
- Throughput (wall clock)
- 556.2M ops/s556.2M ops/s over the thread's CPU time
- Thread CPU time / wall time
- 1.000 (threshold 0.900)Below 1, the thread was not running for part of its slices (quota, neighbours, hypervisor steal when counted, JVM pauses). Close to 1 proves nothing.
- Spread from second to second
- 8.4 % (threshold 40 %)p10 528.3M · p50 563.9M · p90 575.7M ops/s over 9 seconds
- GC pauses during the measurement
- 0 ms (threshold 50 ms)0 collections, 0 ms of collection time
- Highest current CPU frequency
- 5,335 MHz (24 CPUs read)advertised maximum: 5,658 MHz
Witnesses of the single-core test (plugin 2.5.0). The score does not read this test, and none of these figures changes the run's stability verdict.
Host, memory and server state
- Time a task waited for storage
- 0.9 % (all tasks at once: 0.9 %)includes the disk test, which waits for storage by design: not judged for the run
- Time a task stalled on memory
- 0 % (all tasks at once: 0 %) (threshold 5 %)
- CPU quota during the run
- 7.5 coresno change observed
- Container memory
- peak 12,306 MiBlimit events: high 0 · max 0 · OOM kills 0
- Runnable tasks on the machine
- up to 17.3 on average during a test, for 24 logical CPUs
- Host uptime at the start
- 4,449 h
- Server at the start of the run
- JVM up for 1 minfirst bench since the JVM startedoutside the bench world: 0 players · 289 chunks · 158 entities
Run pressures from plugin 2.4.0, the rest from plugin 2.6.0. None of these figures changes the score or the run's stability verdict; the diagnosis names the tests they concern.
Thresholds and their reasons are published in the benchmark methodology. Rules rc-6.
Every measurement
Each test in full. Tests in trouble are open; the others fold to their summary line.
Single-Core Stress
RedstoneHealthy20.00 TPS13.4 ms35.3s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection18 collections, 870ms total
Percentiles and stability
Raw data (68 fields)
Block PhysicsUnstable19.86 TPS17.7 ms25.5s
Single-core stress via falling-block physics.
- Heavy garbage collection18 collections, 1064ms total
- The run did not hold steadyTPS P1=10.00<15, TPS min=10.00 (50% of avg)
Percentiles and stability
Raw data (69 fields)
Exploration
Chunk LoadingUnstable19.90 TPS7.1 ms7.3s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection27 collections, 6162ms total
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (59 fields)
Chunk TickingHealthy20.00 TPS25.0 ms41.9s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection18 collections, 1334ms total
Percentiles and stability
Raw data (63 fields)
Lighting UpdateHealthy20.00 TPS3.4 ms25.5s
Lighting recomputation throughput on block place / break.
- Heavy garbage collection18 collections, 1263ms total
Percentiles and stability
Raw data (62 fields)
Entities
Mob AICritical5.21 TPS237.4 ms31.6s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Heavy garbage collection22 collections, 2454ms total
- The run did not hold steadyTPS avg=5.21<19, TPS P1=5.00<15
Percentiles and stability
Raw data (79 fields)
Mechanics
HopperHealthy19.98 TPS3.0 ms19.2s
Intensive hopper chain item transfers.
- Heavy garbage collection18 collections, 1084ms total
Percentiles and stability
Raw data (70 fields)
ExplosionHealthy20.00 TPS5.8 ms17.2s
Massive TNT explosions and block destruction.
- Heavy garbage collection18 collections, 800ms total
Percentiles and stability
Raw data (112 fields)
Ticking Tile EntitiesHealthy19.96 TPS5.6 ms36.8s
Many ticking tile entities (furnaces, hoppers, etc.).
- Heavy garbage collection18 collections, 1242ms total
Percentiles and stability
Raw data (62 fields)
World SaveHealthy20.00 TPS2.3 ms4.8s
World save speed and TPS impact during save operations.
- Heavy garbage collection18 collections, 678ms total
Percentiles and stability
Raw data (58 fields)
Bone Meal GrowthHealthy20.00 TPS2.6 ms23.6s
Rapid crop and tree growth via bone meal.
- Heavy garbage collection9 collections, 403ms total
Percentiles and stability
Raw data (62 fields)
CPU
Single-Core (tick-aligned)Healthy20.00 TPS4.2 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
- Heavy garbage collection18 collections, 730ms total
Percentiles and stability
Raw data (65 fields)
Multi-Core CPUHealthy19.99 TPS2.7 ms13.1s
Parallel computation throughput across worker threads.
- Heavy garbage collection9 collections, 365ms total
Percentiles and stability
Raw data (58 fields)
Memory & Storage
Memory PerformanceHealthy19.99 TPS3.4 ms31.1s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection36 collections, 1413ms total
Percentiles and stability
Raw data (58 fields)
Disk PerformanceHealthy20.00 TPS3.1 ms38.3s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection9 collections, 394ms total
Percentiles and stability
Raw data (57 fields)
Network
Network (NBT)Unstable19.85 TPS25.6 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection23 collections, 1070ms total
- The run did not hold steadyTPS P1=10.00<15, TPS min=10.00 (50% of avg)
Percentiles and stability
Raw data (57 fields)
›Machine and serverAMD Ryzen 9 9900X 12-Core Processor · Paper · 26.3
Score Breakdown
Detailed sub-category scores