mirror of
https://github.com/PaperMC/Paper.git
synced 2024-12-28 07:20:24 +01:00
60026267e3
By default, spigot shifts chat over to an unbounded thread pool, on a normal server, this really offers no gains, the creation of a thread on submitting to the pool on these servers eats more time vs just running it in the netty pipeline, however, on servers using plugins which do work in here, there could be some overall benefits to moving this stuff outside of the pipeline. In general, this patch does two things: 1) Exposes the core size for the pool, this allows for ensuring that a number of threads sit around in the pool, mitigating the need for creating new threads; This IS however caveated, the ThreadPoolExecutor will ONLY create core threads as they're needed, it just won't allow for us to dip back under the # of core threads, this can potentially be mitigated by calling prestartCoreThread, however, I'm not sure if there is much justification for this 2) Exposes a max size for the pool, as stated, by default this is unbounded, for most servers limiting the size of the pool is going to have 0 effects given how fast chat is actually processed, this is honestly really just exposed for the misnomers or people who just wanna ensure that this won't grow over a specific size if chat gets stupidly active |
||
|---|---|---|
| .. | ||
| patches/sources | ||
| src | ||
| .gitignore | ||
| build.gradle.kts | ||
| LGPL.txt | ||
| LICENCE.txt | ||