Dylan K. Taylor 6bd1491b8b AsyncPool: Apply a cooldown to workers to cut down unnecessary GC lag spikes ...

Since 3.2 there have been some runtime performance issues related to garbage collection and dynamic AsyncWorker booting. This is partly because of GC being dumb about shutting down what it thinks are "unused" workers. A worker which has been idle for a single tick is considered the same as a worker which has been idle for hours. The result of this is that on active servers, workers would get shut down and then immediately restarted because of something like chunk sending. Since booting an async worker is frightfully expensive, this causes lag spikes, which is obviously bad.

This commit changes the GC mechanism to only shutdown workers which have not been used for the last 5 minutes.

2019-01-03 15:06:53 +00:00

..

pocketmine

AsyncPool: Apply a cooldown to workers to cut down unnecessary GC lag spikes

2019-01-03 15:06:53 +00:00