So up until now I’ve been using mpm_itk or mpm_peruser – both with advantages and disadvantages in an attempt to secure web content. Both of these is essentially a forking mpm, kills Keepalive to a greater or lesser extent, and almost as important – neither is supported by mainline apache (so you’re on you own). Personally I prefer mpm_worker (or more recently mpm_event) since it’s threaded, and I find that it uses less resources (in terms of memory mostly). A lot of movement has also been happening with respect to FastCGI and the advantages are very good, both in terms of security and reliability (in theory).
Read the rest of this entry »
Using php-fpm and mod_proxy_fcgi to optimize and secure LAMP servers
January 16th, 2013
Outlook hamstrunged ULS progress
August 24th, 2012I’m not one for highly controversial titles. But today Outlook wasted a couple of hours of my life. Instead of posting big explanations I think I’ll rather let the pictures do the talking:
Read the rest of this entry »
DSL (iBurst) bonding options
April 24th, 2012So recently I started getting a lot of inquiries about ADSL line bonding and decided it was time to start investigating. Various options have presented itself, but very few true solutions.
Read the rest of this entry »
Preventing GCC from trashing the system
December 31st, 2011I’ve recently seen GCC processes consuming as much as 1GB RAM for it’s resident set size (ie, what it actually consumes in memory). I also have an i7 processor, which means I’d like to run compiles at -j8 and higher (to compensate slightly for disk IO). I have 4GB of RAM. Now, at 8 processes, each consuming 512MB of RSS, I’m starting to push into swap quite considerably, resulting in much slower actual compiles, and I can just as well be using -j2 wasting a LOT of resources by it just sitting there and not getting utilized. A plan had to be made. Read the rest of this entry »
