Benchmark Report
Nothing crossed a threshold
No measurement of this run points to a defect. That describes this run under this load, not every load.
Weakest test: Mob AI, 10.8 TPS on average. The 15 other tests hold at least 19.76 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
59%
of the 5 servers running Paper & forks on Minecraft 26.3
Total score 116,347 · group median 113,274
- Single Core
Better than 80% · 179,140 vs median 162,013 · Top quarter
- Gameplay
Better than 80% · 71,250 vs median 69,627 · Top quarter
- Exploration
Better than 80% · 98,778 vs median 81,949 · Top quarter
- Entities
Better than 76% · 85,886 vs median 79,161 · Top quarter
- Mechanics
Better than 0% · 44,174 vs median 46,746 · Bottom quarter
- Hardware
Better than 27% · 39,649 vs median 48,150
- Memory
Better than 52% · 32,344 vs median 32,225
- Disk
Better than 1% · 24,777 vs median 53,110 · Bottom quarter
- Multi-Core
Better than 28% · 69,039 vs median 77,101
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 80% · MSPT 6.5 ms vs median 9.1 ms · TPS 20 vs median 20 · Top quarter
- Bone Meal Growth
Better than 80% · MSPT 0.3 ms vs median 1.3 ms · TPS 20 vs median 20 · Top quarter
- Chunk Loading
Better than 80% · MSPT 0.9 ms vs median 4.3 ms · TPS 19.8 vs median 19.7 · Top quarter
- Chunk Ticking
Better than 80% · MSPT 9.7 ms vs median 13 ms · TPS 20 vs median 20 · Top quarter
- Explosion
Better than 80% · MSPT 1.5 ms vs median 3 ms · TPS 19.9 vs median 19.9 · Top quarter
- Hopper
Better than 80% · MSPT 0.7 ms vs median 1.6 ms · TPS 20 vs median 19.9 · Top quarter
- Lighting Update
Better than 80% · MSPT 1.2 ms vs median 1.9 ms · TPS 20 vs median 20 · Top quarter
- Mob AI
Better than 77% · MSPT 100.4 ms vs median 127.4 ms · TPS 10.8 vs median 9.3 · Top quarter
- Redstone
Better than 2% · MSPT 24.4 ms vs median 17.1 ms · TPS 19.8 vs median 15 · Bottom quarter
- Ticking Tile Entities
Better than 80% · MSPT 1 ms vs median 1.8 ms · TPS 20 vs median 20 · Top quarter
- World Save
Better than 80% · MSPT 0.2 ms vs median 1.1 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 Oct 28, 2026, 6:40 AM 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)
Test by test
Problems first — select a row for the full test- Mob AIEntities10.80UnstableUnstable
- RedstoneSingle-Core Stress19.76effective 20.0UnstableUnstable
- Chunk LoadingExploration19.84StableUnstable
- ExplosionMechanics19.85StableUnstable
- Ticking Tile EntitiesMechanics19.99StableHealthy
- Block PhysicsSingle-Core Stress20.00StableHealthy
- Bone Meal GrowthMechanics20.00StableHealthy
- Chunk TickingExploration20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- HopperMechanics20.00StableHealthy
- Lighting UpdateExploration20.00UnstableHealthy
- Memory PerformanceMemory & Storage20.00StableHealthy
- Multi-Core CPUCPU20.00StableHealthy
- Network (NBT)Network20.00StableHealthy
- 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 100.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 100.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": "purpur",
"minecraft": "26.3",
"java": "25.0.5.0.2"
},
"recommendations": [
{
"id": "spigot.portee-activation-monstres",
"family": "spigot",
"measure": "mobAI.mspt.avg",
"value": 100.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": 100.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 (78 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=28 -XX:G1MaxNewSizePercent=50 -XX:G1HeapRegionSize=16M -XX:G1ReservePercent=15 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=3 -XX:InitiatingHeapOccupancyPercent=20 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=0 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -XX:+UnlockDiagnosticVMOptions -XX:+UnlockExperimentalVMOptions -XX:G1SATBBufferEnqueueingThresholdPercent=30 -XX:G1ConcMarkStepDurationMillis=5 -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:+UseTransparentHugePages -XX:LargePageSizeInBytes=2M -XX:+UseLargePages -XX:+EagerJVMCI -XX:+UseStringDeduplication -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:+UseVectorCmov -XX:+UseXMMForArrayCopy -XX:+EliminateLocks -XX:+DoEscapeAnalysis -XX:+AlignVector -XX:+OptimizeFill -XX:+EnableVectorSupport -XX:+UseCharacterCompareIntrinsics -XX:+UseCopySignIntrinsic -XX:+UseVectorStubs -XX:+UseFastStosb -XX:+UseNewLongLShift -XX:+UseXmmI2D -XX:+UseXmmI2F -XX:+UseXmmLoadAndClearUpper -XX:+UseXmmRegToRegMoveAll -XX:UseAVX=2 -XX:UseSSE=4 -XX:+UseCompactObjectHeaders -Xmx5399M -Xms5399M
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. - 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:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=28 -XX:G1MaxNewSizePercent=50 -XX:G1HeapRegionSize=16M -XX:G1ReservePercent=15 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=3 -XX:InitiatingHeapOccupancyPercent=20 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=0 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -XX:+UnlockDiagnosticVMOptions -XX:+UnlockExperimentalVMOptions -XX:G1SATBBufferEnqueueingThresholdPercent=30 -XX:G1ConcMarkStepDurationMillis=5 -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:+UseTransparentHugePages -XX:LargePageSizeInBytes=2M -XX:+UseLargePages -XX:+EagerJVMCI -XX:+UseStringDeduplication -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:+UseVectorCmov -XX:+UseXMMForArrayCopy -XX:+EliminateLocks -XX:+DoEscapeAnalysis -XX:+AlignVector -XX:+OptimizeFill -XX:+EnableVectorSupport -XX:+UseCharacterCompareIntrinsics -XX:+UseCopySignIntrinsic -XX:+UseVectorStubs -XX:+UseFastStosb -XX:+UseNewLongLShift -XX:+UseXmmI2D -XX:+UseXmmI2F -XX:+UseXmmLoadAndClearUpper -XX:+UseXmmRegToRegMoveAll -XX:UseAVX=2 -XX:UseSSE=4 -XX:+UseCompactObjectHeaders -Xmx5399M -Xms5399M -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.
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:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1RSetUpdatingPauseTimePercent=5No 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
- 0.7 % (threshold 15 %)3 timings: 12.1 ms · 12.2 ms · 12.1 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 1.5 %, 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.9 % (threshold 25 %)138 ms
- Time a task waited for a core
- 0 % (threshold 40 %)
Limits seen by the server
- CPU quota
- 4 cores
- CPU set
- 0-31 (32 cores)
- Memory limit
- 8 GiB
- Host logical CPUs
- 4
- Host memory
- 8 GiB
- Container signals
- cgroup-v2-namespace, overlay-root
Storage
- Filesystem
- ext4 · Local filesystem
- Direct 4K reads
- Honoured (93.7 µs against 0.3 µs from cache)
Single-core measurement
- Throughput (wall clock)
- 830.3M ops/s830.3M 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
- 5.1 % (threshold 40 %)p10 809.8M · p50 829.3M · p90 851.8M ops/s over 9 seconds
- GC pauses during the measurement
- 47 ms (threshold 50 ms)3 collections, 47 ms of collection time
- Highest current CPU frequency
- 5,637 MHz (4 CPUs read)advertised maximum: 5,581 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.6 %)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
- 4 coresno change observed
- Container memory
- peak 7,667 MiBlimit events: high 0 · max 0 · OOM kills 0
- Runnable tasks on the machine
- up to 4.6 on average during a test, for 4 logical CPUscontainer values (lxcfs): they say nothing about neighbours
- Server at the start of the run
- JVM up for 40.9 min3 benches 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
RedstoneUnstable19.76 TPS24.4 ms34.8s
Single-core stress via intensive redstone circuit updates.
- Heavy garbage collection15 collections, 51ms total
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (72 fields)
Block PhysicsHealthy20.00 TPS6.5 ms24.8s
Single-core stress via falling-block physics.
Percentiles and stability
Raw data (69 fields)
Exploration
Chunk LoadingUnstable19.84 TPS0.9 ms8.2s
Chunk generation and loading speed across dispersed zones.
- Heavy garbage collection6 collections, 387ms total
- The run did not hold steadyTPS P1=15.00<15
Percentiles and stability
Raw data (61 fields)
Chunk TickingHealthy20.00 TPS9.7 ms40.9s
Server performance when ticking many loaded chunks with random tick updates.
- Heavy garbage collection5 collections, 72ms total
Percentiles and stability
Raw data (63 fields)
Lighting UpdateHealthy20.00 TPS1.2 ms24.6s
Lighting recomputation throughput on block place / break.
Percentiles and stability
Raw data (56 fields)
Entities
Mob AIUnstable10.80 TPS100.4 ms30.2s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
- Heavy garbage collection6 collections, 247ms total
- The run did not hold steadyTPS avg=10.80<19, TPS P1=5.00<15, TPS StdDev=2.86>2, TPS min=5.00 (46% of avg)
Percentiles and stability
Raw data (80 fields)
Mechanics
HopperHealthy20.00 TPS0.7 ms19.0s
Intensive hopper chain item transfers.
Percentiles and stability
Raw data (68 fields)
ExplosionUnstable19.85 TPS1.5 ms17.0s
Massive TNT explosions and block destruction.
- Heavy garbage collection3 collections, 29ms total
- The run did not hold steadyTPS P1=13.85<15, TPS min=13.85 (70% of avg)
Percentiles and stability
Raw data (115 fields)
Ticking Tile EntitiesHealthy19.99 TPS1.0 ms35.9s
Many ticking tile entities (furnaces, hoppers, etc.).
Percentiles and stability
Raw data (58 fields)
World SaveHealthy20.00 TPS0.2 ms4.8s
World save speed and TPS impact during save operations.
Percentiles and stability
Raw data (56 fields)
Bone Meal GrowthHealthy20.00 TPS0.3 ms23.3s
Rapid crop and tree growth via bone meal.
Percentiles and stability
Raw data (60 fields)
CPU
Single-Core (tick-aligned)Healthy20.00 TPS2.2 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
- Heavy garbage collection3 collections, 47ms total
Percentiles and stability
Raw data (65 fields)
Multi-Core CPUHealthy20.00 TPS0.2 ms14.7s
Parallel computation throughput across worker threads.
Percentiles and stability
Raw data (56 fields)
Memory & Storage
Memory PerformanceHealthy20.00 TPS0.2 ms23.1s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
- Heavy garbage collection4 collections, 9ms total
Percentiles and stability
Raw data (58 fields)
Disk PerformanceHealthy20.00 TPS0.3 ms105.0s
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)Healthy20.00 TPS13.6 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
- Heavy garbage collection6 collections, 16ms total
Percentiles and stability
Raw data (56 fields)
›Machine and serverAMD Ryzen 9 9950X3D2 16-Core Processor · Purpur · 26.3
Score Breakdown
Detailed sub-category scores