Disable Nether cities from BetterNether due to server freezes during auto save
NLBlacky opened this issue · 16 comments
Modpack version:
2.2.0
Describe the request:
Disable Nether cities from BetterNether by default for server/client files. This is the option B:CityEnabled=false in betternether.cfg. BetterNether has been giving alot of server performance issues (freezes from 5 seconds up to a minute) since it is trying to write alot of data from cities to a file during every world save, even if there were no changes since last auto save. More details can be found in this Github issue report in BetterNether Github. This is an example of one of my own Spark tests that will show that there is a very high CPU usage when the world is being saved, caused by BetterNether.
Reasons why this should be added:
It has taken me and many others alot of time to figure out why our servers were performing soo badly every now and then. Only after figuring out it was during the auto save and after monitoring the auto save we noticed that BetterNether was using up loads of CPU during the saving, which caused the server freezes (5 seconds and more). It would save others alot of debugging time if this config setting would be disabled by default in this modpack. I even think that singleplayer performance might be improved as I suspect they will have freezes as well, but less noticeable than servers.
Additional context:
I'm unsure if there is any quest progression that will require the Nether cities. If there is, I would highly suggest to adjust those quests as it is not worth the constant freezes.
Another server (LvLmeUP community) with 5-10 players , disabling nether cities instantly removed a 4 second lagspike each 40s that has been sticking with the server for a long time
I just wanted to confirm this fix from another server owner. We have a server with a regular population of 6+ players, and we were experiencing massive lag spikes repeatedly that made the server nearly unplayable.
After disabling the nether city generation and regenerating the nether from scratch, we can confirm that our repeating lag spikes have vanished and the server is back to a playable state. I would highly recommend this be made a default config change so that future people running a server will not have to experience and diagnose this issue. Thank you for your time and for bringing this issue to light, our community is extremely grateful.
Nether cities are not required for progression. I highly recommend disabling them, as this pattern of lag spike was also occurring in the beta test server, making it extremely hard to play at times, and likely was caused by the same issue.
@Pexon94 No, just disable city generation in the config file. BetterNether is still needed for quests
How do I disable the BetterNether mod? Everytime someone joins the nether, the server just dies.
Please try to avoid long discussions here about server performance when the issue doesn’t seem related to this topic. Feel free to ping me (NLBlacky) in DJ2 Discord (servers channel) so we can start troubleshooting your issue.
I disabled BetterNether City generation an generated a new Nether and the server still laggs and then dies... I don´t know what to do to be honest
@Pexon94 Can you post your error log and spark profile along with the specs of the server (including how much RAM is given to DJ2)? Also, exactly which config did you disable in the betternether.cfg file?
crash-2021-09-09_14.02.10-server.txt
The server got 16 gbs of RAM, the other specs I can´t tell..But it runs smoothly until the nether.
I just disabled the generation for Nether Cities, thats all
Oh, have the server owner set max-tick-time to -1 in the server.properties file. That will fix the "crashes" (the game is taking longer than a minute which is the default watchdog limit (time which the server will restart if a tick takes longer than))
Don't know what else to try as my server doesn't have this issue. (docker container with a 3900X + 6-10GB allocated + ran off nvme store)
