Direct answer

Low TPS is determined by tick-time pressure, not the total CPU percentage displayed by a panel. One busy tick thread can be the bottleneck even when overall CPU is below 100%.

Identify the failing layer

A tick has limited time to complete even if the machine reports free capacity on other CPU cores.

First checks and evidence

  • Measure TPS and MSPT while players experience lag.
  • Capture a spark profile during the busy period and identify world ticks, entities, chunk operations or expensive plugin tasks.

Admin diagnosis and repair

  1. Compare the busiest thread with CPU quotas, clock throttling and competing processes on a shared host.
  2. Optimize the measured workload or move to stronger per-core performance; retest before increasing view/simulation distance.

Verify the fix: Check that average and spike MSPT improve under a comparable player and entity load.

Important safety note

Adding threads or RAM will not automatically make a single overloaded region or main tick thread finish faster.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000