1 critical, 2 warnings 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.
Fabric48.1ms per tick (budget 50ms)17.39 TPS1569 entities
Profile from spark.lucko.me/6I5rHp1ozA
minecraft is using 1247% of server-thread time.
Of the server-thread time this profile sampled, 1247% sits inside minecraft. Behind it: c2me-base at 9%, lithium at 9%. 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.
TPS is 17.39 against a target of 20.
The server is completing 17.39 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.
Garbage collection is running every 25463s, averaging 284.7ms.
The G1 Young Generation collector is running every 25463s and averaging 284.7ms. 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 DiscordRun a community? Add the Roastd bot and anyone can roast a crash log in your support channel.
Add the Roastd botGot a server of your own that deserves a second opinion?
Roast your own serverRoastd 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.