TickWait

TickWait

How long does your server wait for a CPU?

When the machine under your server is busy, the main thread queues for a core and every tick starts late — and nothing in the console shows it. TickWait reads the kernel's own counters for the main thread once a second and tells you how long it waited and why:

• at your plan's CPU limit — the server's cgroup was throttled,
• behind your server's own threads — garbage collection, chunk workers, plugins,
• other work on the same cores — other servers, the host.

On current Paper and its forks it also splits every tick into CPU work, waiting for a CPU, and the rest.

Commands

/tickwait status · /tickwait report · /tickwait export · /tickwait share · /tickwait unshare <id> — all need tickwait.admin (operators by default).

What leaves your server

Nothing, unless you run /tickwait share and confirm. Then it uploads per-hour CPU, tick and player-count sums, the CPU model, CPU count and limit, cgroup version, OS, kernel, Java and server versions, and any host/plan labels you set to truetick.gg, and prints a public link (not indexed by search engines). Not the server's address, player names, the world or chat. /tickwait export shows the exact upload first; /tickwait unshare <id> deletes it.

Requirements

Linux, Paper, Spigot, Purpur or another Paper fork, Java 8 or newer. Run on: Paper 1.21.11 and Purpur 1.21.11 (per-second and per-tick split), Spigot 1.21.11 and Paper 1.8.8 (per-second split). Folia isn't supported yet.

How to read the numbers, with calibration runs: https://truetick.gg/tickwait · Source (MIT): https://github.com/truetick-gg/tickwait

Made by TrueTick, a Minecraft host. It measures every host the same way, ours included. TickWait was written with Claude, Anthropic's AI, and tested on TrueTick's servers.