Do you some figures around improvement from changing thread_handling to a pool instead of one per thread?
The queries on my db server, fit the documented use case for this feature - lots of short live queries.
The queries on my db server, fit the documented use case for this feature - lots of short live queries.
It doesn't make sense for all workloads, but I have found thread pool to be useful in cases where application servers can overload database servers (either via misconfigured connection pooling, or no pooling).
An example where it might make less sense: a dedicated worker queue running in N threads connecting to MySQL.