Roastd The verdict is in. 2 crit1 warn Roast your own server

TPS is 14.61 against a target of 20.

2 critical, 1 warning 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.

Fabric41.7ms per tick (budget 50ms)14.61 TPS1581 entities

Profile from spark.lucko.me/qpaZcZywBA

critical

TPS is 14.61 against a target of 20.

The server is completing 14.61 ticks a second where it should manage 20. Everything timed in ticks slows with it: crop growth, furnaces, mob AI and redstone. On Fabric the standard fix is Lithium for the tick loop, FerriteCore for memory, and C2ME if chunk generation is the cost.

critical

minecraft is using 1143% of server-thread time.

Of the server-thread time this profile sampled, 1143% sits inside minecraft. Behind it: lithium at 5%. Check its config for the expensive features first, update it, and if the cost stays where it is, take it out and profile again to confirm it was the cause.

warning

Garbage collection is running every 31753s, averaging 403ms.

The G1 Young Generation collector is running every 31753s and averaging 403ms. Each pause is a tick the server does not get. If the heap is also near full, fix that first. If it is not, tuned G1 flags are the usual answer: search for an Aikar flags generator and use the output for your heap size.

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.