StackMob-3
StackMob-3 copied to clipboard
Server lagging with stackmob
Hi!
I am having issues with the plugin StackMob, it stacks the mobs into 50 (each stack), but the server still lags because of high amount of mobs, I even tried higher numbers 150-200 the result is the same. Here is a timing that displays all the info about the plugin and the server. https://timings.aikar.co/?id=1a3552417d07452bbcfb876b756b8131#timings
I'm not entirely sure if it's the same issue, forgive me if it's not...
Up until recently, I had immense entity lag on my server, even with 0 players online! Turns out StackMob's Cache file was extremely bloated with -1 value entities. Even with 0 players online, ticking entities destroyed the server's TPS.
Our lag issues resolved IMMEDIATELY after running the StackMob command /sm cleanup
This removed all of the -1 entities from the cache file.
We've been using YML for the cache.
Running the command returned this result:
Timings Before Running /sm cleanup
Timings After Running /sm cleanup
I don't have a cleanup command it says "StackMob >> Error: Incorrect command parameters!"
I have a server of 2-3 active players (5 at most) prepping for a new server. Been using StackMob for a month and the server has started to degrade in performance.
I ran timings and found this:
I ran /sm cleanup
with 800k entities and timed out the server.
Ran the timings again and got this.
After a server reboot and cleaning the cache, we aren't getting any more lag spikes. Does StackMob automatically run the cleanup, or is this something server administrators need to include in their maintenance process?
I have a server of 2-3 active players (5 at most) prepping for a new server. Been using StackMob for a month and the server has started to degrade in performance.
I ran timings and found this:
I ran
/sm cleanup
with 800k entities and timed out the server.Ran the timings again and got this.
After a server reboot and cleaning the cache, we aren't getting any more lag spikes. Does StackMob automatically run the cleanup, or is this something server administrators need to include in their maintenance process?
in theory, that command should only need to be ran once.