A.14.1: What is the Thread Pool and what problem does it solve?
A.14.2: How does the Thead Pool limit and manage concurrent sessions and transactions for optimal performance and throughput?
A.14.3: How is the Thread Pool different from the client side Connection Pool?
A.14.4: When should I use the Thread Pool?
A.14.5: Are there recommended Thread Pool configurations?
Questions and Answers
The MySQL Thread Pool is a MySQL server plugin that extends the default connection-handling capabilities of the MySQL server to limit the number of concurrently executing statements/queries and transactions to ensure that each has sufficient CPU and memory resources to fulfill its task. Commercial distributions of MySQL 5.5 and 5.6 include the Thread Pool plugin.
The default thread-handling model in MySQL Server executes statements using one thread per client connection. As more clients connect to the server and execute statements, overall performance degrades. The Thread Pool plugin provides an alternative thread-handling model designed to reduce overhead and improve performance. The Thread Pool plugin increases server performance by efficiently managing statement execution threads for large numbers of client connections, especially on modern multi-CPU/Core systems.
For more information, see Section 8.12.7, “The Thread Pool Plugin”.
The Thread Pool uses a “divide and conquer” approach to limiting and balancing concurrency. Unlike the default connection handling of the MySQL Server, the Thread Pool separates connections and threads, so there is no fixed relationship between connections and the threads that execute statements received from those connections. The Thread Pool then manages client connections within configurable thread groups, where they are prioritized and queued based on the nature of the work they were submitted to accomplish.
For more information, see Section 126.96.36.199, “Thread Pool Operation”.
The MySQL Connection Pool operates on the client side to ensure that a MySQL client does not constantly connect to and disconnect from the MySQL server. It is designed to cache idle connections in the MySQL client for use by other users as they are needed. This minimizes the overhead and expense of establishing and tearing down connections as queries are submitted to the MySQL server. The MySQL Connection Pool has no visibility as to the query handling capabilities or load of the backend MySQL server. By contrast, the Thread Pool operates on the MySQL server side and is designed to manage the execution of inbound concurrent connections and queries as they are received from the client connections accessing the backend MySQL database. Because of the separation of duties, the MySQL Connection Pool and Thread Pool are orthogonal and can be used independent of each other.
MySQL Connection Pooling via the MySQL Connectors is covered in Chapter 23, Connectors and APIs.
There are a few rules of thumb to consider for optimal Thread Pool use cases:
variable keeps track of the number of concurrent statements
currently executing in the MySQL Server. If this variable
consistently exceeds a region where the server won't operate
optimally (usually going beyond 40 for InnoDB workloads), the
Thread Pool will be beneficial, especially in extreme parallel
If you are using the
limit the number of concurrently executing statements, you will
find the Thread Pool solves the same problem, only better, by
assigning connections to thread groups, then queuing executions
based on transactional content, user defined designations, and
Lastly, if your workload comprises mainly short queries, the Thread Pool will be beneficial.
To learn more, see Section 188.8.131.52, “Thread Pool Tuning”.
The Thread Pool has a number of user case driven configuration parameters that affect its performance. To learn about these and tips on tuning, see Section 184.108.40.206, “Thread Pool Tuning”.