MySQL Forums
Forum List  »  InnoDB

Woocommerce my.cnf phpmysql
Posted by: Iain Macandrew
Date: February 05, 2018 04:24PM

Firstly I'm an open uni student studying IT, I'm really new and trying to learn as much as possible, over the weekend I feel I have read more than I did the entire previous year.

I'm looking for some advice/guidance help

I'm trying to optimise a database using the my.cnf file and I am not sure what I am doing wrong but none of the below is working

What am I doing wrong and what recommendations would you suggest for my.cnf config

Currently running woocommerce, not a huge amount of products less than 100 but some products have almost 10,000 variations.

I'm currently using wp-import to import products but it is becoming pretty slow. I currently have around 500k variations on the db with 450k of these contained within post data.

I'm currently running a VPS on OVH, 2 cores 8gb ram. Website is low traffic 75-100 visitors a day. using CentOS 6.9 and Plesk.

Disks are SSD ram not being used 4gb only one cpu core is being used phpmysql version 7.0.27

What would be the best config for my site currently only have the below;


# Disabling symbolic-links is recommended to prevent assorted security risks


query_cache_type = 1
query_cache_limit = 256K
query_cache_min_res_unit = 2k
query_cache_size = 80M

key_buffer = 1G

table_cache = 256
table_definition_cache = 256

wait_timeout = 120
connect_timeout = 120
interactive_timeout = 120

innodb_flush_method = O_DIRECT
innodb_flush_log_at_trx_commit = 2
innodb_file_per_table = 1
innodb_buffer_pool_size = 1G

Thank you for taking time to read my post.

Options: ReplyQuote

Written By
Woocommerce my.cnf phpmysql
February 05, 2018 04:24PM
February 06, 2018 11:35AM
February 06, 2018 01:53PM
February 06, 2018 03:55PM
February 06, 2018 04:28PM
February 06, 2018 08:15PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.