Roastd The verdict is in. 2 crit Roast your own server

Ticks are taking 999ms against a 50ms budget.

2 critical found. Every finding below comes from what was actually in the pasted files. Treat the fixes as suggestions: they cover the common causes, and this case may need more digging.

Paper999ms per tick (budget 50ms)1 TPS46155 entities

Profile from spark.lucko.me/7eCXveR2GV

critical

Ticks are taking 999ms against a 50ms budget.

The server thread is averaging 999ms per tick against a budget of 50ms. The worst tick in that window was 1325.2ms. A tick that runs past the budget is time the server cannot give back, and it shows up to players as rubber-banding and slow block breaking. The heaviest chunk in this profile holds 32567 entities, which is the first thing to look at.

critical

32567 entities are sitting in one chunk at -12, 67.

world chunk -12, 67 (around x -192, z 1072) holds 32567 entities: 30748 item, 1819 snow_golem. Every one of them is ticked, so a single chunk like this can hold the whole server back, and it is 71% of the 46155 entities in the profile. Go to those coordinates and look for a mob farm without a killing layer, an item backlog on the floor, or a bred animal pen nobody culls. The next worst are world chunk -12, 66 (around x -192, z 1056) and world chunk -13, 67 (around x -208, z 1072).

Need more help or want to discuss your issue further? Join our Discord and bring the link to this page.

Join our Discord

Run a community? Add the Roastd bot and anyone can roast a crash log in your support channel.

Add the Roastd bot

Got a server of your own that deserves a second opinion?

Roast your own server

Roastd reads spark reports but is not affiliated with spark or PaperMC. spark is by lucko.

Roastd is a free tool built by Hostd. This diagnosis stays put. The log it was read from is deleted on a timer.