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, 17.25 TPS on average. The 15 other tests hold at least 19.98 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 estimated›+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 AIEntities17.25ModerateHealthy
- Chunk LoadingExploration19.98ModerateHealthy
- HopperMechanics19.99StableHealthy
- Multi-Core CPUCPU20.00StableHealthy
- Block PhysicsSingle-Core Stress20.00StableHealthy
- Network (NBT)Network20.00ModerateHealthy
- Bone Meal GrowthMechanics20.00StableHealthy
- Disk PerformanceMemory & Storage20.00StableHealthy
- Chunk TickingExploration20.00StableHealthy
- Lighting UpdateExploration20.00StableHealthy
- Memory PerformanceMemory & Storage20.00StableHealthy
- ExplosionMechanics20.00StableHealthy
- Single-Core (tick-aligned)CPU20.00StableHealthy
- Ticking Tile EntitiesMechanics20.00StableHealthy
- RedstoneSingle-Core Stress20.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 (22 arguments)
Values of system properties, agents and file paths are never shown: they appear as <redacted>.
-Xms50G -Xmx50G -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
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
RedstoneHealthy20.00 TPS1.2 ms32.0s
Single-core stress via intensive redstone circuit updates.
Percentiles and stability
Block PhysicsHealthy20.00 TPS3.8 ms20.0s
Single-core stress via falling-block physics.
Percentiles and stability
Exploration
Chunk LoadingHealthy19.98 TPS2.2 ms20.0s
Chunk generation and loading speed across dispersed zones.
Percentiles and stability
Chunk TickingHealthy20.00 TPS1.9 ms40.9s
Server performance when ticking many loaded chunks with random tick updates.
Percentiles and stability
Lighting UpdateHealthy20.00 TPS0.7 ms24.6s
Lighting recomputation throughput on block place / break.
Percentiles and stability
Entities
Mob AIHealthy17.25 TPS0.7 ms27.2s
Complex mob AI behaviours (villagers, iron golems, hostile mobs).
Percentiles and stability
Mechanics
HopperHealthy19.99 TPS0.2 ms19.1s
Intensive hopper chain item transfers.
Percentiles and stability
ExplosionHealthy20.00 TPS0.5 ms17.0s
Massive TNT explosions and block destruction.
Percentiles and stability
Ticking Tile EntitiesHealthy20.00 TPS0.4 ms35.9s
Many ticking tile entities (furnaces, hoppers, etc.).
Percentiles and stability
World SaveHealthy20.00 TPS0.3 ms4.9s
World save speed and TPS impact during save operations.
Percentiles and stability
Bone Meal GrowthHealthy20.00 TPS0.6 ms21.9s
Rapid crop and tree growth via bone meal.
Percentiles and stability
CPU
Single-Core (tick-aligned)Healthy20.00 TPS1.4 ms10.0s
Single-thread compute throughput measured on the main thread under the tick scheduler.
Percentiles and stability
Multi-Core CPUHealthy20.00 TPS0.4 ms2.6s
Parallel computation throughput across worker threads.
Percentiles and stability
Memory & Storage
Memory PerformanceHealthy20.00 TPS0.4 ms170.2s
RAM bandwidth and latency.
JVM measurements — do not reflect actual bare-metal performance.
Percentiles and stability
Disk PerformanceHealthy20.00 TPS0.5 ms17.1s
Sequential and random 4K read/write performance.
JVM measurements — do not reflect actual bare-metal performance.
Percentiles and stability
Network
Network (NBT)Healthy20.00 TPS18.0 ms20.0s
Serialisation throughput — proxy for the rate at which the server can ship world data to clients.
Percentiles and stability
›Machine and serverAMD Ryzen 9 9950X 16-Core Processor · Purpur · 1.21.11
Score Breakdown
Detailed sub-category scores