Benchmark Report
Tick spikes · Network (NBT)
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 15.2 ms
- mspt_p99 = 94.86 ms
- spike_ratio = 6.24 ratio
- sample_count = 92 count
- spike_ticks = 9 count
- spike_window_ticks = 420 count
- spike_threshold_ms = 50 ms
- spike_ticks_with_gc = 1 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 626.4 ms
- spike_gc_pause_ms = 9 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, 19.74 TPS on average. The 15 other tests hold at least 19.78 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
92%
of the 14 servers running Paper & forks on Minecraft 26.3
Total score 138,228 · group median 86,059
Top quarter- Single Core
Better than 92% · 196,024 vs median 122,524 · Top quarter
- Gameplay
Better than 92% · 80,261 vs median 62,238 · Top quarter
- Exploration
Better than 77% · 96,661 vs median 78,508 · Top quarter
- Entities
Better than 92% · 118,361 vs median 70,158 · Top quarter
- Mechanics
Better than 75% · 46,683 vs median 46,271 · Top quarter
- Hardware
Better than 56% · 46,579 vs median 45,500
- Memory
Better than 57% · 28,267 vs median 25,021
- Disk
Better than 18% · 22,720 vs median 39,388 · Bottom quarter
- Multi-Core
Better than 73% · 106,995 vs median 72,746
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 68% · MSPT 7.7 ms vs median 12.5 ms · TPS 20 vs median 20
- Bone Meal Growth
Better than 77% · MSPT 0.5 ms vs median 1.7 ms · TPS 19.9 vs median 20 · Top quarter
- Chunk Loading
Better than 78% · MSPT 1.6 ms vs median 4.6 ms · TPS 20 vs median 19.4 · Top quarter
- Chunk Ticking
Better than 60% · MSPT 15.2 ms vs median 21.4 ms · TPS 20 vs median 20
- Explosion
Better than 71% · MSPT 2.2 ms vs median 3.9 ms · TPS 19.9 vs median 19.9
- Hopper
Better than 80% · MSPT 0.8 ms vs median 2.6 ms · TPS 20 vs median 19.9 · Top quarter
- Lighting Update
Better than 54% · MSPT 1.5 ms vs median 2 ms · TPS 20 vs median 20
- Mob AI
Better than 92% · MSPT 25.3 ms vs median 169.7 ms · TPS 19.7 vs median 7.2 · Top quarter
- Redstone
Better than 92% · MSPT 16.2 ms vs median 24.3 ms · TPS 20 vs median 19.5 · Top quarter
- Ticking Tile Entities
Better than 65% · MSPT 2.4 ms vs median 3.7 ms · TPS 20 vs median 20
- World Save
Better than 73% · MSPT 0.4 ms vs median 1.4 ms · TPS 20 vs median 20
Scored with version 8.3.0 of the scoring rules. Groups of fewer than 5 servers are never used. Updated Nov 1, 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 = 15.2 ms
- mspt_p99 = 94.86 ms
- spike_ratio = 6.24 ratio
- sample_count = 92 count
- spike_ticks = 9 count
- spike_window_ticks = 420 count
- spike_threshold_ms = 50 ms
- spike_ticks_with_gc = 1 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 626.4 ms
- spike_gc_pause_ms = 9 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 4 (default 10)
Tick spikes
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 25.3 ms
- mspt_p99 = 51.16 ms
- spike_ratio = 2.02 ratio
- sample_count = 115 count
- spike_ticks = 33 count
- spike_window_ticks = 495 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 = 2,680.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
Test by test
Problems first — select a row for the full test- Network (NBT)Network19.78UnstableCritical
- Mob AIEntities19.74UnstableUnstable
- Bone Meal GrowthMechanics19.94StableUnstable
- ExplosionMechanics19.94StableUnstable
- Block PhysicsSingle-Core Stress20.00StableHealthy
- Chunk LoadingExploration20.00ModerateHealthy
- Chunk TickingExploration20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- HopperMechanics20.00StableHealthy
- Lighting UpdateExploration20.00UnstableHealthy
- Memory PerformanceMemory & Storage20.00StableHealthy
- Multi-Core CPUCPU20.00StableHealthy
- RedstoneSingle-Core Stress20.00effective 20.0UnstableHealthy
- 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.
Nothing to change: no measurement in this report crosses a threshold where a documented setting would help.
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 (27 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 -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=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true -Xmx11729M -Xms11729M
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. - Removed
-XX:-UnlockExperimentalVMOptionsearlier occurrence; the JVM keeps -XX:+UnlockExperimentalVMOptions.
java -XX:ThreadPriorityPolicy=1 -XX:+EnableJVMCIProduct -XX:+EnableJVMCI -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=1 -Xmx11729M -Xms11729M -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 2 other arguments (system properties, agents): keep them between java and -jar. Their values are not shown here.
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
- 0 % (threshold 15 %)3 timings: 12.4 ms · 12.2 ms · 12.2 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 2.2 %, 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)
- CPU time stolen by the hypervisor
- 0 % (threshold 5 %)
- Scheduling periods ended throttled by the quota
- 1.1 % (threshold 25 %)59.9 ms
- Time a task waited for a core
- 0 % (threshold 40 %)
Limits seen by the server
- CPU quota
- 8 cores
- CPU set
- 0-31 (32 cores)
- Memory limit
- 16 GiB
- Host logical CPUs
- 8
- Host memory
- 16 GiB
- Container signals
- cgroup-v2-namespace, overlay-root
Storage
- Filesystem
- ext4 · Local filesystem
- Direct 4K reads
- Honoured (102.3 µs against 0.4 µs from cache)
Single-core measurement
- Throughput (wall clock)
- 827.9M ops/s827.7M 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
- 6.6 % (threshold 40 %)p10 804.5M · p50 839.6M · p90 860M 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,623 MHz (8 CPUs read)advertised maximum: 5,579 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
- 2.6 % (all tasks at once: 2.5 %)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
- 8 coresno change observed
- Container memory
- peak 14,077 MiBlimit events: high 0 · max 0 · OOM kills 0
- Runnable tasks on the machine
- up to 10.2 on average during a test, for 8 logical CPUscontainer values (lxcfs): they say nothing about neighbours
- Server at the start of the run
- JVM up for 13.1 min1 bench before this oneoutside the bench world: 0 players · 289 chunks · 1 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-7.
Every measurement
Each test in full. Tests in trouble are open; the others fold to their summary line.
Single-Core Stress
RedstoneHealthy20.00 TPS16.2 ms34.9s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection6 collections, 28ms total
Percentiles and stability
Raw data (68 fields)
Block PhysicsHealthy20.00 TPS7.7 ms24.9s
Single-core stress via falling-block physics.
Percentiles and stability
Raw data (69 fields)
Exploration
Chunk LoadingHealthy20.00 TPS1.6 ms7.4s
Chunk generation and loading speed across dispersed zones.
- memory_budget: no full GC observed by the pre-flight check, projected peak heap at 83.2%
- Heavy garbage collection2 collections, 137ms total
Percentiles and stability
Raw data (59 fields)
Chunk TickingHealthy20.00 TPS15.2 ms41.0s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection5 collections, 65ms total
Percentiles and stability
Raw data (63 fields)
Lighting UpdateHealthy20.00 TPS1.5 ms24.6s
Lighting recomputation throughput on block place / break.
Percentiles and stability
Raw data (56 fields)
Entities
Mob AIUnstable19.74 TPS25.3 ms30.3s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Heavy garbage collection4 collections, 57ms total
- The run did not hold steadyTPS P1=15.00<15, TPS min=10.00 (51% of avg)
Percentiles and stability
Raw data (79 fields)
Mechanics
HopperHealthy20.00 TPS0.8 ms19.0s
Intensive hopper chain item transfers.
- Heavy garbage collection3 collections, 46ms total
Percentiles and stability
Raw data (70 fields)
ExplosionUnstable19.94 TPS2.2 ms17.0s
Massive TNT explosions and block destruction.
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (111 fields)
Ticking Tile EntitiesHealthy20.00 TPS2.4 ms36.0s
Many ticking tile entities (furnaces, hoppers, etc.).
Percentiles and stability
Raw data (58 fields)
World SaveHealthy20.00 TPS0.4 ms4.8s
World save speed and TPS impact during save operations.
Percentiles and stability
Raw data (56 fields)
Bone Meal GrowthUnstable19.94 TPS0.5 ms23.3s
Rapid crop and tree growth via bone meal.
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (61 fields)
CPU
Single-Core (tick-aligned)Healthy20.00 TPS2.4 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
Percentiles and stability
Raw data (63 fields)
Multi-Core CPUHealthy20.00 TPS0.3 ms7.8s
Parallel computation throughput across worker threads.
Percentiles and stability
Raw data (56 fields)
Memory & Storage
Memory PerformanceHealthy20.00 TPS0.3 ms25.1s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
Percentiles and stability
Raw data (56 fields)
Disk PerformanceHealthy20.00 TPS0.5 ms114.5s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
Percentiles and stability
Raw data (55 fields)
Network
Network (NBT)Critical19.78 TPS15.2 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection5 collections, 20ms total
- The run did not hold steadyTPS P1=10.00<15, TPS min=10.00 (51% of avg)
Percentiles and stability
Raw data (59 fields)
›Machine and serverAMD Ryzen 9 9950X3D2 16-Core Processor · Purpur · 26.3
Score Breakdown
Detailed sub-category scores