• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Question MySQL 5.5 configuration

Kapnos

Basic Pleskian
Hi,

I'm using Plesk Onyx with MySQL 5.5.53 for hosting a news site based on wordpress with WP Super Cache on a dedicated server with 32GB RAM and 2x250GB SSD RAID1. Can you give some advice for my.cnf for best performance? I have this settings for now:
Code:
join_buffer_size        = 2M
tmp_table_size          = 64M
max_heap_table_size     = 64M
innodb_buffer_pool_size = 8G
innodb_log_buffer_size  = 8M
key_buffer              = 32M
max_allowed_packet      = 32M
thread_stack            = 192K
thread_cache_size       = 8
myisam-recover         = BACKUP
max_connections        = 800
query_cache_limit       = 8M
query_cache_size        = 64M

and after running mysqltuner I get these results:
Code:
Variables to adjust:
    query_cache_type (=0)
    query_cache_size (> 64M)
    join_buffer_size (> 2.0M, or always use indexes with joins)
    tmp_table_size (> 64M)
    max_heap_table_size (> 64M)
    table_open_cache (> 400)
    innodb_file_per_table=ON
    innodb_log_file_size should be equals to 1/4 of buffer pool size (=2G) if possible.
    innodb_buffer_pool_instances(=8)
 
Sounds more like a question for a MySQL performance tuning forum than for a Plesk forum.

Optimal MySQL performance settings are strongly determined by the actual usage and behavior of scripts. Noone can tell you if the above settings are good for your or not. The settings that a single execution of Mysqltuner determines are one out of many possible sets. As I understand Mysqltuner it is essential to continuously monitor the script and database actions by it to derive best performance settings from new data as they are logged. Running Mysqltuner next week for example might yield better values, because more data becomes available over time. For example, if a specific function that requires a large buffer is only execute once a week, your might not have caught it yet, so you won't know that your buffer size is too small.
 
Back
Top