commit b7bcd20c1f94f13ef6bcf3bd39c0647c81791f1b
author Shevchik <Shev4ik.den@gmail.com> Thu Mar 12 16:12:23 2020 +0300
committer Shevchik <Shev4ik.den@gmail.com> Thu Mar 12 16:12:23 2020 +0300
tree 3b681d2d0ec67d6695b09f0821ea0f68410e022c
parent ebe85569a2e4e645e6b0121c23e53e6a5f752134

Use own pool instead of netty recycler

Netty recycler can grow to insane sizes and that can't be controlled
from the code itself. Netty also supports recycling objects in a thread
that is different from allocating one, and growing the pool, but we
don't need this.
In our own pool we set the total max capacity to 200 (can be changed
using system property), which should be enough to hold ~200 players
(because usually transformation does 1 server packet -> 1 packet data).