Direct answer

For a traditional Paper server, strong sustained single-thread CPU performance matters for tick work; parallel jobs, chunk generation and Folia regions have different scaling behavior.

Recommended procedure

  1. List target Minecraft version, server software, mods/plugins, player count, world generation and view/simulation distance.
  2. Record expected peak concurrent players, technical farms, redstone, worldborder travel and any proxies or database services.
  3. Budget Java heap plus native and OS RAM, low-latency SSD storage, verified backups and network protection.

What to change

  1. Prefer benchmarking a representative world/workload on a candidate host over trusting marketing GHz or vCPU counts.
  2. Request clear information on shared versus dedicated CPU, CPU quotas, RAM limit and disk IOPS.
  3. Plan upgrade headroom and monitor MSPT, GC, chunk-load times, storage errors and network packet loss after deployment.

How to verify the result

Test a staged representative peak workload and keep hardware only if TPS/MSPT, memory headroom, backup throughput and player connection quality meet your target.

Version and safety notes

RAM calculators are estimates, not guarantees. Modpacks, render distance, plugin architecture and shared hosting contention can change resource needs greatly; Folia should not be advertised as a universal multithread speedup.

Official references

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