Magento Performance Optimized Server

Published on Author gryzliLeave a comment

I’ve read some articles on magento performance tuning and server optimization for best result. Here I will try to summarize most of the important stuff I’ve read.


Server Software

Magento best practices advice on using the following configuration:

Nginx + MySQL + php-fpm (FastCGI) + APC / OpCache + (Varnish)

It’s better to use as recent as possible versions of MySQL and PHP.


MySQL configuration tunning

The following my.cnf content is suggested here:




NGINX Server optimization

Below are some configuration snippets, which must bring to performance gains when using Nginx.






Magento CMS Configuration

There are some steps we can take inside the Magento itself in order to bring better performance to our magento optimized store.

Full Page Cache

Full page cache gives Magento the ability to cache the whole page and store it in form of (X)HTML. Only CMS, Category and Product View support Full Page cache.

Enabling Full Page cache inside Magento (or through plugin) could lead to very high performance gains:

– up to 10x performance gain on CMS Page

– up to 100% performance gain on Shopping Scenario

– up to 10x performance gain on Browsing Scenario


System Caching

The default system caching method is by using files on disk. Changing this method to APC or Memcache could result in some performance gains also.

This setting can be modified in: app/etc/local.xml config file


Session Handling

The default session storage for storing client sessions is disk storage.  If you want to achieve better performance, you can configure Magento to store it’s sessions in Memcached . 

Keep in mind, that when using just a single server, the performance benefits of using Memcached as a session storage are almost none.


Rebuilding Indexes

The time for index rebuilding must be chosen carefully and configured to happen during least loaded times.


Using Solr as a Search Engine

Since v1.8, Magento Enterprise Edition supports Apache Solr search engine and provides a module called: “Enterprise Search“, which could be configured to use Solr instead of MySQL Full text search.




Leave a Reply

Your email address will not be published. Required fields are marked *

Captcha * Time limit is exhausted. Please reload CAPTCHA.