-
New Feature
-
Resolution: Invalid
-
Minor
-
None
-
None
-
Latest
-
Yes
I apologize in advance for possible mistakes, I am not a native speaker of this language
In the implementation of BukkitScheduler - CraftScheduler executor is CachedThreadPool and this is not a good idea, CachedThreadPool on the one hand is good that it will always do the job, but it is also bad at the same time. Thread is the most expensive in the Concurrent World and thoughtless creation of it can have a bad effect on performance, so I just sent a message to the console every 10 ticks with the output of the name of the current thread, I have reached hundreds and continues to grow, I suggest choosing ForkJoinPool or FixedThreadPool