Excessive plugin consumption (1.15.2)
- I've been testing the plugin on spigot 1.15.2 and had to remove it after a few minutes, with only 50 users it was able to drop the tps to 11.0
IMAGE:
Comments (17)
-
-
repo owner It’s true the plugin was never designed with larger servers in mind.
I’m gonna see what I can do to improve it. But as with the plugin version the server has to do calculations that realistically should happen distributed on the clients I suspect I will not be able to improve much.
-
Or is there a way in the plugin's configuration to improve performance?
-
repo owner There are some limited options (lowering the scanning size), but I don’t expect them to be enough for 50+ players.
I’ve got one idea to improve performance, but that will be a bigger rewrite and take a few days still.
-
Ok cool
-
repo owner Please try this version (delete the old config files before running) and report back with performance.
I switched to a more limited but hopefully way more performant configuration / condition system. (No more JavaScript, just premade conditions - it’s basically now using the same config file I use to generate the datapack version)
-
Ok I'll implement it again and let you know the results.
-
I'll try it out in a few weeks with even more players now I can't because of lack of time.
-
repo owner - attached Mambience-2.0.0-20w22a-noAssets.jar
-
I see you sent me the plugin again, is it a new version or is it the same?
-
repo owner It’s basically the same with a small change to scheduling to hopefully spread the load out more evenly.
So in theory it should be just a slight bit better with larger numbers of players than the previous upload, but in practice it will probably not matter much.
-
Well, I have already been trying the previous version and so far I have had no complaints about lag, I will still try the new version, thank you very much for the help.
By the way, if I am going to update the plugin should I restart the configuration again?
-
repo owner Between the two uploads on this ticket?
Then there is no reason to reset the config. In general resetting is only required if a version comes with sound changes AND you want to use them, but because Version 2 now uses a completely different system the old config files were incompatibl.
-
repo owner - changed status to resolved
"Fixed" or drastically improved in Version 2. Will wait and test 1.16 (Fabric) compatibility before official release.
-
“Between the two uploads on this ticket?” Yes
-
I mean, if I have to update the settings to use the new file you attached, I'm using the first version you attached, but I want to update to the new one.
-
repo owner That is what I meant. You don’t have to do anything else but change the plugin jar.
English is not my first language, so I’m sorry my previous message was unclear.
- Log in to comment
https://imgur.com/BQ9XgN4