So let’s continue our attempt to improve Magento’s performance and this time around let’s focus on the web server itself. There are a bunch of web servers out there but the most known are, a least to me: Apache, Nginx and Lighttpd My favorite, and of course I am biased here, is Nginx and it approach to serving content. As you may all know Nginx is an event-based web server and the main advantage of this asynchronous approach is scalability. ...
So you recently launched your PHP application (read Magento) just to realize that it is really slow even though you have state of the art hardware, software and it is configured to kick ass. You decided to install varnish to help full page caching and your CDN, which it only has gzipped merged and minified assets, to serve content faster now your site seems to be flying but New Relic still reveals so many bottlenecks specially for the fillers you needed to keep some dynamic content rocking. ...
Sharing knowledge is always a good idea. Lately I have been doing lots of integration with Varnish and Magento with different clients and it will be interesting to find out if you have any ideas or suggestions (read improvements) to make it better and ultimately help the community even more: Setting up varnish in switch mode: In my home directory I always have a bash aliases (vim ~/.bash_aliases) file where I add the following iptable rules: ...
Did you ever want to create a redirect in a Magento Store without having to use htacess? Using Observers and the powerful Request and Response objects from Zend Framework you can. In this example I will show how you can do it. First you need to create the module, more on module creations here: http://goo.gl/vvT2j. Create a directory under app/code/community and name it FooBar, then create another directory under FooBar and name it Redirect. Create two directories inside FooBar: etc and Model. ...