Magento Site Performance Optimization

Tuning, Scaling, and Replicating MySQL
Physical Memory : 1.95 G
Max memory limit exceeds 90% of physical memory
As a reminder, the configuration on which I ran the script was not the default
one but a misconfigured one in order to check the benefits of the
recommendation system.
Tuning my.cnf for performance
As a base to work with, my advice will be to generate the configuration file by
using the MySQL tuning Primer script by analyzing a real production server. Then,
copy the generated files onto your development server in order to test out the
recommendation of the script. After that, you can use the MySQL tuner.pl script
and add the additional recommendation.
Follow the next steps to add the additional recommendation:
1. Run the Primer script on your production server.
2. Make sure it generates a my.cnf file.
3. Copy this file to your development environment.
4. Replace the /etc/mysql/my.cnf file of your environment server with the
one generated by the Run Primer, and then play around with your Magento
in order to generate new usage statistics of your database engine.
5. Run the mysqltuner.pl script on your production environment and add the
new recommendation to your my.cnf file.
Then, follow the recommendations given here; they are targeting better
performances for Magento:
• innodb_buffer_pool_size: This should be around 50 percent of the
physical server RAM when the server hosts the web server and the database
engine both. If MySQL has its own server, then the allocated RAM should be
80 percent of the total physical RAM.
• innodb_thread_concurrency: This must be two more than twice the
number of your CPUs. This means that on a true dual core, the value must
be 2 x 2 + 2 = 6.
• thread_concurrency: This should be equal to three times the number
of CPUs.
• query_cache_size: This should be 64 MB.
• query_cache_limit: This should be 2 MB.
[ 44 ]
www.it-ebooks.info