Those of you running Slackware 14 or current probably have noticed the move to the Apache httpd v2.4 already.
On my webservers I haven’t yet dared to upgrade from the stable 2.2 version, but I figured it might be a good time to test out an upgrade procedure.
Notable problems / changes
This new version of the Apache httpd brings a few things that you should really pay attention to before attempting to upgrade. Well, you could ignore it, but it would surprise me if you wouldn’t end up with a broken webserver 😉
So you might want to look into these things:
- Configuration syntax changes
- Handling the Pleuris-Hoeren-Paaltjes aka PHP disaster
- Switching to the MPM-event module
A few weeks ago I implemented a FastCGI setup for a magento website. (details Here). That site also runs google analytics.
Here’s what analytics had to show about the speed of the site:
Can you guess when FastCGI was enabled? 😉
For those of you who are graphically challenged, the above graph shows a loading time of 2.1-2.5 seconds on the left and then crashes down to only 1.0-1.3 seconds at the date that I enabled FastCGI. Neat huh? 🙂
Google analytics also notes that “this site is faster than 83% of the sites”, whatever that means. Oh well, we’re happy.
As I love to tinker around with apache/php installations to get them to work as fast as possible while still keeping some security in tact, I found myself messing around with FastCGI today. But why?! Here’s why:
On this machine I previously installed suPhP to get php scripts to run as a normal unix user instead of user apache (so users have the ability to completely lock out their database settings etc for other users on that machine). However, to speed stuff up on a magento webshop I wanted to have a PHP opcode cache running (I tried out APC). (continue reading…)