Enable or disable stacking based on TPS hysteresis #99
Conversation
|
any chance this could be reviewed? |
|
|
||
| this.stackingBasedOnPerformance = ConfigurationManager.Setting.PERFORMANCE_TPS_TOGGLE.getBoolean(); | ||
| if(this.stackingBasedOnPerformance){ | ||
| Bukkit.getServer().getScheduler().runTaskAsynchronously(rosePlugin, new Runnable() { |
There was a problem hiding this comment.
Why is creating this done in an async task?
| @Override | ||
| public void run() { | ||
| if(ConfigurationManager.Setting.PERFORMANCE_TPS_TOGGLE.getBoolean()){ | ||
| Bukkit.getScheduler().runTaskTimerAsynchronously(rosePlugin, () -> { |
There was a problem hiding this comment.
You need to assign async repeating tasks to a variable and ensure they are cancelled when the plugin shuts down. See how the autosave task is handled in this class.
Additionally, as it is now, since this never gets cancelled and gets run every time /rs reload gets run, you can end up with multiple of these tasks running at once, that's bad.
| Bukkit.getServer().getScheduler().runTaskAsynchronously(rosePlugin, new Runnable() { | ||
| @Override | ||
| public void run() { | ||
| if(ConfigurationManager.Setting.PERFORMANCE_TPS_TOGGLE.getBoolean()){ |
There was a problem hiding this comment.
Not sure why this is being checked again? You checked it above and had a variable assigned to it, but aren't using that variable here.
| public void run() { | ||
| if(ConfigurationManager.Setting.PERFORMANCE_TPS_TOGGLE.getBoolean()){ | ||
| Bukkit.getScheduler().runTaskTimerAsynchronously(rosePlugin, () -> { | ||
| double[] tps = Bukkit.getServer().getTPS(); |
There was a problem hiding this comment.
Server#getTPS() is a Paper-API method and this will throw an error on Spigot servers. I believe it's only possible to check the server TPS using NMS on Spigot servers, so that functionality will need to be added to all the NMSHandler interface and implemented for each handler.
|
I currently dont have the time to make the changes mentioned, but if someone can look into this, it would make for a very good feature <3 |
I tested using Stress, using
/stress test=entity amount=5000 duration=120 range=10This is a pretty basic PR, I didn't want to add too many options so I wouldn't over-complicate it. Right now the TPS check runs every 30 seconds using
runTaskAsynchronouslyfrom theStackManagerclass. Maybe it would be nice to add the option so the end user can also check the frequency. For now I guess it gets the job done.The feature is disabled by default, kicking in at 16TPS, and disabling measures after 18TPS is reached.
I added the disabled status using
isEntityStackingTemporarilyDisabled, so I didn't have to modify every single class.