Benchmark Report
Tick spikes · Mob AI
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 27.5 ms
- mspt_p99 = 56.78 ms
- spike_ratio = 2.06 ratio
- sample_count = 93 count
- spike_ticks = 24 count
- spike_window_ticks = 501 count
- spike_threshold_ms = 53.1 ms
- spike_ticks_with_gc = 2 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 3,722.3 ms
- spike_gc_pause_ms = 34.5 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: Chunk Loading, 19.32 TPS on average. The 15 other tests hold at least 19.68 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
63%
of the 5 servers running Paper & forks on Minecraft 1.21
Total score 106,415 · group median 96,794
- Single Core
Better than 62% · 144,009 vs median 137,527
- Gameplay
Better than 80% · 72,802 vs median 68,677 · Top quarter
- Exploration
Better than 0% · 74,780 vs median 84,192 · Bottom quarter
- Entities
Better than 80% · 116,040 vs median 84,011 · Top quarter
- Mechanics
Better than 80% · 46,249 vs median 42,063 · Top quarter
- Hardware
Better than 40% · 44,221 vs median 50,868
- Memory
Better than 0% · 19,442 vs median 25,490 · Bottom quarter
- Disk
Better than 13% · 40,884 vs median 55,851 · Bottom quarter
- Multi-Core
Better than 63% · 97,373 vs median 71,561
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 42% · MSPT 12.9 ms vs median 11.5 ms · TPS 20 vs median 20
- Bone Meal Growth
Better than 37% · MSPT 2.4 ms vs median 1.8 ms · TPS 20 vs median 20
- Chunk Loading
Better than 22% · MSPT 7.3 ms vs median 6.1 ms · TPS 19.3 vs median 19.7 · Bottom quarter
- Chunk Ticking
Better than 38% · MSPT 16.8 ms vs median 15.2 ms · TPS 20 vs median 20
- Explosion
Better than 21% · MSPT 6.9 ms vs median 4.7 ms · TPS 20 vs median 19.9 · Bottom quarter
- Hopper
Better than 55% · MSPT 2.6 ms vs median 2.9 ms · TPS 20 vs median 19.9
- Lighting Update
Better than 31% · MSPT 2.4 ms vs median 2.1 ms · TPS 20 vs median 20
- Mob AI
Better than 80% · MSPT 27.5 ms vs median 110.2 ms · TPS 19.7 vs median 10 · Top quarter
- Redstone
Better than 77% · MSPT 15.4 ms vs median 21.9 ms · TPS 20 vs median 20 · Top quarter
- Ticking Tile Entities
Better than 80% · MSPT 3.1 ms vs median 3.7 ms · TPS 20 vs median 20 · Top quarter
- World Save
Better than 80% · MSPT 1.3 ms vs median 1.5 ms · TPS 20 vs median 20 · Top quarter
Scored with version 8.3.0 of the scoring rules. Groups of fewer than 5 servers are never used. Updated Nov 1, 2026, 12:40 PM UTC. Community trends · All measurements by CPU
What matters
Read from the measurements, never estimatedNon-default server configuration
Compare with care against a server running default settings.
- view-distance 6 (default 10)
- simulation-distance 4 (default 10)
- spawn-limit.monster 5 (default 70)
+6 more modified settings
Tick spikes
The worst ticks are several times the mean. Average TPS stays fine while players feel the stutter.
- mspt_avg = 27.5 ms
- mspt_p99 = 56.78 ms
- spike_ratio = 2.06 ratio
- sample_count = 93 count
- spike_ticks = 24 count
- spike_window_ticks = 501 count
- spike_threshold_ms = 53.1 ms
- spike_ticks_with_gc = 2 count
- spike_ticks_with_throttle = 0 count
- spike_ticks_with_steal = 0 count
- spike_tick_ms = 3,722.3 ms
- spike_gc_pause_ms = 34.5 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
›+2 more findings
When the run started, players or many entities were present outside the bench world. The server ticks them during the tests, so part of each tick went to that world rather than to the workload measured.
- players_online = 1 count
- chunks_loaded_outside_bench = 937 count
- spawn_chunks_loaded_outside_bench = 0 count
- entities_outside_bench = 247 count
- worlds_loaded = 5 count
- players_online_threshold = 1 count
- entities_threshold = 1,200 count
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 = 883 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- Chunk LoadingExploration19.32UnstableUnstable
- Mob AIEntities19.68UnstableUnstable
- Network (NBT)Network19.95StableUnstable
- HopperMechanics19.98StableHealthy
- Block PhysicsSingle-Core Stress20.00ModerateHealthy
- Bone Meal GrowthMechanics20.00StableHealthy
- Chunk TickingExploration20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- ExplosionMechanics20.00ModerateHealthy
- Lighting UpdateExploration20.00StableHealthy
- Memory PerformanceMemory & Storage20.00StableHealthy
- Multi-Core CPUCPU20.00StableHealthy
- RedstoneSingle-Core Stress20.00effective 20.0StableHealthy
- 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 (64 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-XX:ActiveProcessorCount=16 -Djdk.virtualThreadScheduler.parallelism=<redacted> -Djdk.virtualThreadScheduler.maxPoolSize=<redacted> -Xms10240M -Xmx10240M -XX:+UnlockExperimentalVMOptions -XX:+UnlockDiagnosticVMOptions -XX:+AlwaysPreTouch -XX:+PerfDisableSharedMem -XX:+UseNUMA -XX:-DontCompileHugeMethods -XX:MaxNodeLimit=240000 -XX:NodeLimitFudgeFactor=8000 -XX:ReservedCodeCacheSize=400M -XX:NonNMethodCodeHeapSize=12M -XX:ProfiledCodeHeapSize=194M -XX:NonProfiledCodeHeapSize=194M -XX:NmethodSweepActivity=1 -XX:+UseFastUnorderedTimeStamps -XX:+UseCriticalJavaThreadPriority -XX:AllocatePrefetchStyle=3 -XX:+AlwaysActAsServerClassMachine -XX:LargePageSizeInBytes=2M -XX:+EagerJVMCI -XX:+UseAES -XX:+UseAESIntrinsics -XX:+UseFMA -XX:+UseLoopPredicate -XX:+RangeCheckElimination -XX:+OptimizeStringConcat -XX:+UseCompressedOops -XX:+UseThreadPriorities -XX:+OmitStackTraceInFastThrow -XX:+RewriteBytecodes -XX:+RewriteFrequentPairs -XX:+UseFPUForSpilling -XX:+UseFastStosb -XX:+UseNewLongLShift -XX:+UseVectorCmov -XX:+UseXMMForArrayCopy -XX:+UseXmmI2D -XX:+UseXmmI2F -XX:+UseXmmLoadAndClearUpper -XX:+UseXmmRegToRegMoveAll -XX:+EliminateLocks -XX:+DoEscapeAnalysis -XX:+AlignVector -XX:+OptimizeFill -XX:+EnableVectorSupport -XX:+UseCharacterCompareIntrinsics -XX:+UseCopySignIntrinsic -XX:+UseVectorStubs -XX:UseSSE=4 -XX:+UseFastJNIAccessors -XX:+UseInlineCaches -XX:+SegmentedCodeCache --add-modules=jdk.incubator.vector -Dterminal.jline=false -Dterminal.ansi=true -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:-ClassUnloadingWithConcurrentMark -XX:MaxGCPauseMillis=20 -Xlog:gc*:file=<redacted>:time,uptime,level,tags:filecount=3,filesize=8M
Nothing to correct: every option is valid for Java 25.
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.
-XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+DisableExplicitGC -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.
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.
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
- 4.6 % (threshold 15 %)3 timings: 14.4 ms · 14.2 ms · 14.8 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 11.6 %, 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
- not measured (threshold 25 %)0 ms
- Time a task waited for a core
- 0.9 % (threshold 40 %)
Limits seen by the server
- CPU quota
- none (no limit at any level)
- CPU set
- 0-15 (16 cores)
- Memory limit
- 21.6 GiB
- Host logical CPUs
- 16
- Host memory
- 31.3 GiB
- Container signals
- dockerenv, cgroup-v2-namespace, overlay-root, pterodactyl-env
Storage
- Filesystem
- ext4 · Local filesystem
- Direct 4K reads
- Honoured (115.8 µs against 1.2 µs from cache)
Single-core measurement
- Throughput (wall clock)
- 465.4M ops/s468.3M ops/s over the thread's CPU time
- Thread CPU time / wall time
- 0.994 (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
- 14.3 % (threshold 40 %)p10 436.6M · p50 498.1M · p90 507.8M 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
- not exposed by this systemadvertised maximum: 4,300 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
- 7 % (all tasks at once: 6.8 %)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
- not measuredno change observed
- Container memory
- peak 13,855 MiBlimit events: high 0 · max 0 · OOM kills 0
- Runnable tasks on the machine
- up to 14.8 on average during a test, for 16 logical CPUs
- Host uptime at the start
- 145.3 h
- Server at the start of the run
- JVM up for 14.7 minfirst bench since the JVM startedoutside the bench world: 1 players · 937 chunks · 247 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 TPS15.4 ms35.6s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection7 collections, 59ms total
Percentiles and stability
Raw data (65 fields)
Block PhysicsHealthy20.00 TPS12.9 ms25.7s
Single-core stress via falling-block physics.
- Heavy garbage collection7 collections, 70ms total
Percentiles and stability
Raw data (68 fields)
Exploration
Chunk LoadingUnstable19.32 TPS7.3 ms8.0s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection10 collections, 419ms total
- The run did not hold steadyTPS P1=10.00<15, TPS min=10.00 (52% of avg)
Percentiles and stability
Raw data (58 fields)
Chunk TickingHealthy20.00 TPS16.8 ms41.8s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection12 collections, 183ms total
Percentiles and stability
Raw data (60 fields)
Lighting UpdateHealthy20.00 TPS2.4 ms25.7s
Lighting recomputation throughput on block place / break.
- Heavy garbage collection7 collections, 73ms total
Percentiles and stability
Raw data (56 fields)
Entities
Mob AIUnstable19.68 TPS27.5 ms31.5s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Heavy garbage collection13 collections, 167ms total
- The run did not hold steadyTPS P1=10.00<15, TPS min=10.00 (51% of avg)
Percentiles and stability
Raw data (78 fields)
Mechanics
HopperHealthy19.98 TPS2.6 ms19.4s
Intensive hopper chain item transfers.
- Heavy garbage collection11 collections, 110ms total
Percentiles and stability
Raw data (68 fields)
ExplosionHealthy20.00 TPS6.9 ms17.5s
Massive TNT explosions and block destruction.
- Heavy garbage collection6 collections, 35ms total
Percentiles and stability
Raw data (112 fields)
Ticking Tile EntitiesHealthy20.00 TPS3.1 ms37.0s
Many ticking tile entities (furnaces, hoppers, etc.).
- Heavy garbage collection8 collections, 83ms total
Percentiles and stability
Raw data (57 fields)
World SaveHealthy20.00 TPS1.3 ms4.7s
World save speed and TPS impact during save operations.
- Heavy garbage collection6 collections, 58ms total
Percentiles and stability
Raw data (55 fields)
Bone Meal GrowthHealthy20.00 TPS2.4 ms23.8s
Rapid crop and tree growth via bone meal.
- Heavy garbage collection3 collections, 18ms total
Percentiles and stability
Raw data (59 fields)
CPU
Single-Core (tick-aligned)Healthy20.00 TPS3.9 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
- Heavy garbage collection6 collections, 51ms total
Percentiles and stability
Raw data (60 fields)
Multi-Core CPUHealthy20.00 TPS1.6 ms9.8s
Parallel computation throughput across worker threads.
- Heavy garbage collection3 collections, 16ms total
Percentiles and stability
Raw data (55 fields)
Memory & Storage
Memory PerformanceHealthy20.00 TPS1.3 ms33.2s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection12 collections, 63ms total
Percentiles and stability
Raw data (55 fields)
Disk PerformanceHealthy20.00 TPS1.3 ms75.7s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection4 collections, 20ms total
Percentiles and stability
Raw data (54 fields)
Network
Network (NBT)Unstable19.95 TPS25.8 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection5 collections, 27ms total
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (56 fields)
›Machine and serverAMD Ryzen 9 9950X 16-Core Processor · Purpur · 1.21.11
Score Breakdown
Detailed sub-category scores