How to Boost Magento Speed on Localhost/XAMPP

cachelocalhostmagento-1.9performancexampp

I have checked that Magento is running such slowly on localhost although my php.ini has the requirements to run Magento. However, its low performance and speed lack make my work so much slow and I would like to hear from you how I can speed up Magento locally, maybe installing some cache extension or something else like Memcached, Xcache or APC.

I'm on Windows 10 and xampp.

Best Answer

When developing localy on windows there are two common causes of delay, resolution of localhost is one and windows slow file operations due to complex OS ACL is the other.

To improve the situation you must replace every localhost entry in your magento installation with 127.0.0.1. Some people make an entry in their windows hosts file that allows localhost to be redirected to 127.0.0.1 , this will improve file serving time but php commands like PDO connect will still produce one second delay each until 127.0.0.1 has replaced localhost in settings.

To avoid windows slow file operations you need a opcode cache php accelerator like APC or WinCache. When developing in windows you can activate IIS and use Microsoft Web Platform Installer to install/configure PHP, MYSQL and WinCache in few clicks. When using xampp you can install APC with http://downloads.php.net/pierre/ or http://dev.freshsite.pl/php-accelerators/apc.html binaries or building APC with Visual Studio and then configure with directions from internet. From my experience last WinCache version is extremely fast and it is a real safe choice for windows. Very few developers i know use IIS instead of apache due to the bad past of IIS but at this time it is easier to setup, can handle more requests and it is faster in most parts when compared to apache in windows.

With those 2 changes you will see a 1000%-20000% improvement while configuring MySQL for production wont benefit a development environment at all. Tweaking cache and gzip in htaccess wont benefit a local environment either, firstly because you read the files directly from your hard disk (with a cache optimizer from memory) and secondly because it is a dynamic site that you will constantly change during development so you cant set expire times and disable etags.

To improve the speed even more you will have to tweak your template. In few words as all suggest combine all png that you can , convert to base64 the ones you cant combine and use a tool like Lab.js to control loading so you can make sure your page on load is less that 1.5 sec. When moving to production use a CDN to serve media. If all go well everything will be so fast you wont care again about HW benchmarks, DB optimization and hosting comparition until you have many thousands visits per day and serve a lot of content. (Static caching not dynamic pages / parts of pages and using magento cache system for your scripts for ultimate speed ).

P.S. Using windows client version to broadcast a site in the www is legal as long as you don't change the 20 concurrent connection limit in the OS from my understanding while reading the license.

Related Solutions

Magento 1.9 Cache Performance – Fix Extremely Slow Cache Issues

I investigated even more and I think I finally solved the issue. So what can you do to analyse such an issue?

In order to have a good idea when the cache becomes too large and if the problem is really the cache size, add a cronjob which calls the following script e.g. each 15 minutes:

#!/bin/bash

# this script is an attempt to check if the full cache is the real performance problem
# it should be called regularly as a cronjob

cache_dir="/html/shop/var/cache/"
log_file="/html/cache_log"

line=$(date)
line="$line Size of cache directory: $(du -hs $cache_dir)"
echo "$line" >> $log_file

line=$(date)
line="$line Total cache tags: $(find $cache_dir'cm-tags/' -type f | wc -l)"
echo "$line" >> $log_file

Then you can analyse the contents of /html/cache_log to see how the cache size develops, when your page becomes too slow and if the root cause is really the cache.

Analyse your cache files. Therefore, it is quite helpful to write all cache files into a log file with e.g.:
```
ls -R /html/shop/var/cache > /html/cachefiles
```
Have a look at this file and the file names within. What kind of cache files are there? Is there anything suspicious? In my case, there were a whole lot of cache files containing AMSHOPBY in their file name - a reference to the Amasty Improved Navigation (Amasty_Shopby) extension. It was creating a whole lot of cache files. Some of them looked quite weird to me. Disabling the Amasty Improved Navigation cache solved the problem instantly. I contacted their support with a detailed description and the support was really good. The caching strategy was quickly completely overhauled and is now much better. They promised to integrate the patch in the next version of the extension, so every version > 2.8.3 should be fine.

Good luck in finding the root cause for your big cache!

Magento – Site randomly redirecting to localhost

I'll have a guess:

How is your setting in System > Web > URL Options > Auto-Redirect? Is it "302", and if you set it to "301", does the behaviour change (to now being a 301 redirect?).

A few days ago, I had a similar issue when features just stopped to work. The issue was that the disk space of the server was full, so MySQL could not access enough tmp/-space for some queries. This resulted in pages wihout loaded product lists and the like. Maybe, your core_url_rerite table is immensely huge, so that it can not be read, and the setting mentioned above produces a 302.

Best Answer

Related Solutions

Magento 1.9 Cache Performance – Fix Extremely Slow Cache Issues

Magento – Site randomly redirecting to localhost

Related Topic