Book Image

Instant Magento Performance Optimization How-to

By : Nayrolles Mathieu (USD), Mathieu Nayrolles
Book Image

Instant Magento Performance Optimization How-to

By: Nayrolles Mathieu (USD), Mathieu Nayrolles

Overview of this book

The optimization of an attractive commercial website is a non-trivial task that demands time and knowledge. Optimization is a critical point for all growing businesses because a misconfiguration could make you lose money, a lot of money. If your server is overloaded, a browser that wants to turn into a buyer will not be able to, and you will lose customers. "Instant Magento Performance Optimization How-To" is a practical, hands-on guide that provides you with a number of clear, step-by-step exercises to help you reach a high performance level for your Magento stores and keep your customers satisfied.This book looks at tweaks and tips used to boost your Magento Performance, and breaks down the confusion that surrounds the subject.You will learn how to compress your pages, styles, and scripts by almost 80%. We will also take a look at controversial optimization settings such as Magento core compilation or enabling all caching systems. You will discover new applications that improve performance. If you wish your e-businesses to grow and want to keep your customers satisfied, you definitely need this book.
Table of Contents (7 chapters)

Storing your sessions in the database (Should know)

Sessions are mechanisms that allow users to keep their shopping carts safe even if they don't browse our website for a few days. By default, the sessions are saved in the filesystem, and the performance could be improved by storing it in your database.

How to do it...

Open the file named local.xml under app/etc/ and modify line 55 so that it looks like the following line:


How it works...

By default, the sessions are stored in the filesystem under small files, one per session. This option will simply store the contents of these files into the database. This can improve your performance because the database-retrieving process is faster than the filesystem-retrieving process. Another scenario to choose this way of storage is when you have more than one frontend server.