Title: Making Magento run faster configuring Redis as Back-end
1Making Magento run faster with Redis as Back-End
2 About Neev
Key Company Highlights
Web
Mobile
Cloud
Magento eCommerce SaaS Applications Video
Streaming Portals Rich Internet Apps Custom
Development
AWS Consulting Partner Rackspace Joyent
Heroku Google App Engine
iPhone Android Windows Phone 7 HTML5 Apps
250 team with experience in managing offshore,
distributed development.Neev Technologies
established in Jan 05 VC Funding in 2009 By
Basil Partners Part of Publicis Groupe Member
of NASSCOM.Development Centers in Bangalore
and Pune. Offices at Bangalore, USA, Delhi,
Pune, Singapore and Stockholm.
User Interface Design and User Experience Design
Performance Consulting Practices
Quality Assurance Testing
Outsourced Product Development
3 The Caching Method Currently Employed in Magento
- Magento uses the default two level caching of the
Zend framework, a fast cache and a slow one as
configured in the file Local.xml - The fast cache is configured to APC/Memcache,
whereas the slow one is file system based
4 Advantages and Disadvantages of Default Cache
- Magento stores its cache entries in the file
system. This model does have an advantage. We
dont need any additional software to keep it
running - The default model, however, proves to be more of
a disadvantage than an advantage. This is because
Magento stores its cache entries in the file
system in the /var/cache folder. This is fine as
long as the traffic is minimal. The Magento cache
is also organized by tags, this means you have
cache entries which belongs to a cache group - Once the traffic increases, the number of cache
entries in the file system increase, and reading
and writing to the file system becomes slower and
slower - Magento clears cache entries by tag. A typical
scenario is one where, after placing an order or
saving a product, it makes sure that the block
caches are updated on the store. While clearing
entries by cache tag, Magento has to open each
file to check if the cache entry belongs to the
cache group - Consider a Magento store with 1000 products, it
would have a cache size of 50 MB. There would be
at least 3500 entries(individual files) and the
process would be very slow and certainly not
feasible in the long run
52 Ways of Achieving Better Performance in this
Model
- Use SSDs( Solid State Drives) instead of normal
hard drives - Put the /var/cache directory in TMPFs
6 Advantages of Configuring Redis as Back-End
- Very fast cache back end with excellent support
for cache tags, the slower file system cache is
ruled out - Highly recommended in multi-server environments
where you have more than one web server - It has been tested on high traffic Magento stores
with more than 500,000 visitors / day and the
performance has been great
7 Requirements for a Working Redis Back-End
- Redis must be installed on the server.
- PHP Extension PHPRedis must be installed.
- Magento extension Cm_Cache_Backend_Redis must
be installed.
8 Installation and Configuration For Redis
Initial Steps
- Install redis(2.4 required)
- Install phpredis
- Install the magento extension Cm_Cache_Backend_Re
dis - Edit your app/etc/local.xml. Follow screenshot
below
9 Installation and Configuration of Redis Final
Step
- Restart the PHP process and it will make sure
the cache is being stored in Redis as shown below
10Clients
11 Partnerships
12sales_at_neevtech.com
Neev Information Technologies Pvt. Ltd.
Sweden
Singapore
India - Bangalore
USA
India - Pune
Neev AB, Birger Jarlsgatan 53, 6tr, 11145,
Stockholm Phone 46723250723
13 LSquare, 3rd Floor Parihar Chowk,
Aundh, Pune 411007. Phone 91-64103338
The Estate, 121,6th Floor, Dickenson
Road Bangalore-560042 Phone 91 80 25594416
08-03 SGX Centre 2, 4 Shenton Way, Singapore
068807 Phone 65 6435 1961
1121 Boyce Rd Ste 1400,Pittsburgh PA 15241 Phone
1 888-979-7860
For more info on our offerings, visit
www.neevtech.com