You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, segment pools exist only on JVM (on other platforms, implementations are effectively no-op) and behave more like caches than pools.
There are a few directions in which we may/should develop segment pools:
support pools configuration (both in terms of the pool capacity and the size of allocated segments)
make sure every segment is returned to a pool once there are no users remaining
support unlinking a segment from a pool (for scenarios when we have a byte-buffer backed segment and now sending it via Netty -> segment is no longer in use once we "consumed" it by wrapping into a ByteBuf, but it could not be released as a Netty owns it now)
support pool-level isolation (for instance, if there are multiple threads make sure that each of them uses a separate pool, so that data used in one thread would never leak into another thread)
Currently, segment pools exist only on JVM (on other platforms, implementations are effectively no-op) and behave more like caches than pools.
There are a few directions in which we may/should develop segment pools:
This is an epic describing what could be done and tracking progress rather than an instruction to what should be implemented.
The text was updated successfully, but these errors were encountered: