![]() However, some software techniques (eg, better indexes) may help, such as this for WordPress and WooCommerce. Adding RAM is a costly and brute force solution. Big dataset - The system may be I/O-bound.Medium-sized dataset - Most activity is done in RAM the system will run nicely.Tiny dataset - buffer_pool is bigger than necessary -> wasting some of RAM, but so what it is not useful for anything else.There are 3 situations (based on innodb_buffer_pool_size and dataset size): SQL Query Tuner reduced by more than 80 our time to analyze query wait times. Load test in simulated production environments. Profile databases with wait-time analysis. Do not bother changing other settings they add to the complexity of "getting it right". SQL Query Tuner optimizes SQL queries by quickly discovering, diagnosing, and optimizing poor-performing SQL queries.(I often say "set it to 70% of available RAM", but you are asking for more details.) Do adjust innodb_buffer_pool_size such that most of RAM is in use during normal time and even for spikes in activity.Swapping is terrible for MySQL/MariaDB performance. Do not allocate so much RAM that swapping will occur.Looking back through the the MySQL slow log I can see the query below, using the EXPLAIN syntax it looks like all tables are indexed however due to the way its compiled I’m not sure it can be optimised further or in fact where to trace back the query is being ran from - this doesn’t appear in Query Monitor slow logs. Increased WP memory limit from 40MB to 256MB.Query Monitor identified only 1 slow query with a 0.8sec execution.Automatic Platform Optimization for Wordpress installed and up and running.All speed optimisations have been applied.Performance settled down however a few months further on we are beginning to experience spikes in performance again at busy times (circa 300 unique visitors per hour) with the server CPU sat at 100% and the server becoming unresponsive - this can last a couple of minutes currently. Index applied to queries identified in slow query log.installed and made suggested changes to the MySQL configuration.Over recent months we've seen some sporadic performance on the server actions undertaken: The site is a single application and database sat on a Digital Ocean droplet - the box is spec'd as 16 cores / 32 GB RAM / 200GB disk. Wondering if anyone can offer some fresh perspective on some performance issues we're experiencing with a Woocommerce web site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |