Since a month ago, I've not needed to use opis at all. In fact, server TPS has been great. The server has only been up a little more than a month. Recently, we've had a rash of TPS drops before the 4 hour restart. Not mentioning my cron job sometimes fails, curse you CentOS...
Anyhow, as of this moment, my server is becoming almost unplayable. Server tick rate is down to just 6, sometimes 10-11. So as a bench mark test, I went through the world yesterday and broke player's chunk loaders, putting them in chests for later use. Swapped World Anchors for personal anchors, and even nerfed the chickenchunks.cfg to load no more than 25 chunks per loader. So I figured, if the chunks would unload, surely this would fix TPS issues.
My hope was in vain... 15 minutes later, TPS is still less than 10. I then remembered, dynmap. After pausing that, still no change. Then I remembered Extra Utilities, the lava pump, I spent the better part of an hour going through the nether breaking all of them and placing them in a chest for the player. As you can see in the screenshot, only two were left.
As of right now, I'm the only one online and tick rate is absolutely terrible. 6TPS with one player loaded chunk set, which is spawn and no machines etc... (aside from 6 trade-o-mats).
A further investigation with Opis reveals a total update time of 70,000+ updates a second, with the bulk of ticks coming from ThermalExpansion Grid Tick Handler. WHY? Why when no chunks are loaded with TE items does TE need that many ticks??? Is it not properly cleaning up after itself?
Following a reboot, the Grid Tick Handler is under 10,000, and tick rate is once again 19.8TPS
In the following imgur album you can find all the screenshots from opis, aswell as output from the /gc command.
http://imgur.com/a/wPTht
Current modpack: FTB Monster (Recommended)
Server: CentOS 8GB Ram, 6GB allocated to MC
Quad Core CPU 3.2GHz
Jar Flavor: MCPC Plus 1.6.4 R2.1 Forge965 Build 251
Before you say, "you need more ram" notice the ram isn't maxed out, besides if it were, java would crash causing an out of memory issue. There is no excuse for a mod not cleaning up after itself when the chunk unloads...
Has anyone else had this issue?
Anyhow, as of this moment, my server is becoming almost unplayable. Server tick rate is down to just 6, sometimes 10-11. So as a bench mark test, I went through the world yesterday and broke player's chunk loaders, putting them in chests for later use. Swapped World Anchors for personal anchors, and even nerfed the chickenchunks.cfg to load no more than 25 chunks per loader. So I figured, if the chunks would unload, surely this would fix TPS issues.
My hope was in vain... 15 minutes later, TPS is still less than 10. I then remembered, dynmap. After pausing that, still no change. Then I remembered Extra Utilities, the lava pump, I spent the better part of an hour going through the nether breaking all of them and placing them in a chest for the player. As you can see in the screenshot, only two were left.
As of right now, I'm the only one online and tick rate is absolutely terrible. 6TPS with one player loaded chunk set, which is spawn and no machines etc... (aside from 6 trade-o-mats).
A further investigation with Opis reveals a total update time of 70,000+ updates a second, with the bulk of ticks coming from ThermalExpansion Grid Tick Handler. WHY? Why when no chunks are loaded with TE items does TE need that many ticks??? Is it not properly cleaning up after itself?
Following a reboot, the Grid Tick Handler is under 10,000, and tick rate is once again 19.8TPS
In the following imgur album you can find all the screenshots from opis, aswell as output from the /gc command.
http://imgur.com/a/wPTht
Current modpack: FTB Monster (Recommended)
Server: CentOS 8GB Ram, 6GB allocated to MC
Quad Core CPU 3.2GHz
Jar Flavor: MCPC Plus 1.6.4 R2.1 Forge965 Build 251
Before you say, "you need more ram" notice the ram isn't maxed out, besides if it were, java would crash causing an out of memory issue. There is no excuse for a mod not cleaning up after itself when the chunk unloads...
Has anyone else had this issue?