Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
MXS-CAPACITY-Q4-2026
Description
MaxScale currently uses a pool-per-thread approach for connection pooling. This limits the rate of use of the pooled connections and either results in overly large pools that are inefficiently used or creation of short lived connections due to pool capacity running out. Being able to share connections across worker threads, be that by stealing connections or by having one big pool, would alleviate these problems and make the pool size configuration an exact value.
An alternative is to implement stealing from other pools with thread-local pools. This should also result in a self-balancing pooling mechanism.