-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong recommendation "thread_pool_size between 16 and 36 for InnoDB usage" for Percona Server #551
Comments
Hi, Feel free to reopen it if needed |
For Percona Server for MySQL variable Patch to fix this issue and other typos:
|
@jmrenouard, I have no ability to reopen this bugreport, I have only 'Comment' button available. |
Hi, Patch included in 1.8.4 |
@jmrenouard, thanks, but where are two typos:
|
Hi, Patch included in 1.8.4 |
Hi New commit with fix 1.8.5 |
Recommendation "thread_pool_size between 16 and 36 for InnoDB usage"
from MySQL 8.0 Reference Manual / 5.6.3.4 Thread Pool Tuning
is only about Oracle MySQL Enterprise Thread Pool.
If Percona Server used - this recommendation about thread_pool_size MUST be different:
Alexey Stroganov, Performance Engineer at Percona in comments to article Percona Server: Improve Scalability with Percona Thread Pool write: "Usually most efficient value of thread_pool_size is in range between NCPU and NCPU+NCPU/2. NCPU = Number of CPU’s":
MySQLTuner should recommend to use thread_pool_size in range between NCPU and NCPU+NCPU/2. Where NCPU = Number of CPU cores, if Percona Server is used.
Recommendation "thread_pool_size between 16 and 36 for InnoDB usage" should be used only for Oracle MySQL Enterprise Thread Pool and this recommendation is wrong for Percona Server, causing buggy MySQL configurations.
The text was updated successfully, but these errors were encountered: