Direct answer
The Overworld, Nether and End can stress different systems. Terrain exploration, mob AI, redstone machines and plugin activity matter more than the dimension name alone.
How to check it
- Run comparable spark samples while players are active in each dimension. Record exploration speed, new chunk count, entity population and plugin tasks, then identify the dimension-specific workload.
- Record the original configuration or test conditions, capture a profile or a repeatable observation, and identify the affected world or player group.
- Make the measurement under the same player count and workload you will later use to verify the change.
What to change
Pregenerate heavily visited terrain where appropriate and review always-running machines; do not reduce the End or Nether view distance merely because total MSPT rose while someone was exploring.
Test portal transfers and world-specific settings after any change. On multiworld plugins, check which world configuration is truly in effect.
Software and version notes
Check the active version and generated configuration before copying paths or values. Different forks and mod loaders may implement this behavior differently.
This article is written for Paper / compatible servers. Configuration keys and defaults can move between versions. The source material checked for this page includes PaperMC profiling guide. If your server is Folia, Leaf, Purpur, Fabric, Forge, NeoForge, or another fork/loader, do not assume a Paper-only setting exists or behaves identically.
Verify the result
Repeat the same test with the same software build, player count and world activity. Compare the targeted symptom and any spark measurements, then check that intended game mechanics still work. If the change does not produce a reproducible improvement, revert to the recorded baseline.