Tag Archives: php

howto linux

HOWTO install php5-fpm on Debian Squeeze

September 27, 2011 – 7:21 am
PHP5-FPM

PHP5-FPM

Once PHP hit version 5.3, it started shipping with PHP-FPM, which is the new way to handle PHP requests when serving web content. Their site describes it as, “PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites“, but this is being pretty modest when you consider the host of improvements it brings over the old way of doing things when running PHP with an ‘alternate’ webserver such as lighttpd or nginx. So, it sounds like a slam dunk, time to remove all the handwritten fastcgi-php scripts from /etc/init.d, update PHP and go to town, right? Not so fast hot shot, in Debian Squeeze (stable) they don’t include PHP-FPM with PHP 5.3 (reasons for this tend to fall in the ‘not enough testing‘ variety), so we have to look elsewhere for a PHP with this (and other upgrades) enabled. This is exactly what the site and repo Dotdeb is there for, and they have the updated PHP 5.3 that includes the FPM module. So, to get it installed on Debian Squeeze we first have to add the repo line to sources.list

This is a preview of HOWTO install php5-fpm on Debian Squeeze. Read the full post (449 words, 1 image, estimated 1:48 mins reading time)
Tags , , , , , , | Permalink | Comment (1)
commentary featured geek headline linux

Resolving LSIDs with URL resolvers and CouchDB

April 29, 2009 – 8:29 am

346483297_c4cb93ab4e_mRecently I’ve been looking at ways to solve some of biodiversities’ long standing issues with LSIDs, which are, “Life Science Identifiers are a way to name and locate pieces of information on the web. Essentially, an LSID is a unique identifier for some data, and the LSID protocol specifies a standard way to locate the data (as well as a standard way of describing that data). They are a little like DOIs used by many publishers.“  I posted my thoughts to the TDWG discussion mailing list on the topic, and am reprinting it here to allow for further community commentary; Code4lib, I’m looking at you. While much of it is theoretical, it is doable, and if it covers all that needs to be addressed, would be a cool, sustainable way forward for link resolvers for all kinds of usage.

This is a preview of Resolving LSIDs with URL resolvers and CouchDB. Read the full post (935 words, 1 image, estimated 3:44 mins reading time)
Tags , , , , , , , , , , , , | Permalink | Comments (12)
geek howto

HOWTO: determine optimal fastcgi settings for Lighttpd

February 28, 2008 – 11:50 am

PHP Fast-cgiAnyone building a server with a LAMP stack today has tons of options, mine have evolved to using Varnish -> Lighttpd -> Xcache -> PHP5 -> MySQL. Once I had Lighttpd (aka Lighty) installed and running PHP pages I looked to optimize the configuration and push it as hard as possible for more speed. Of course lately I’ve been getting unexplained slowdowns, with many instances of php5-cgi appearing to be taking up almost all of my available CPU on `top`. Reading up on things it appears that I had max_procs, along with PHP_FCGI_CHILDREN, set far too high for the load I’m getting. When you start lighty it gives you the number of processes you’ve define, and then those in turn spawn the number of children you’ve specified. While my settings were too high, they were really overshooting things when you take into account that I’m using Xcache (which provides PHP pre-caching) and Varnish (for HTTP acceleration). So even though one of my dynamic sites that I’m working on to ‘monetize’ things is getting 700-800 hits each day, my caching strategy is taking the load away from the ever available Lighty. Because of this, lighty has much less to do, so giving it a ton of processes to just sit there and eat memory until they’re zombified is a waste. After reading the lighty FAQ and other posts specific to this, I’ve settled on the this for my fastcgi config block within my lighttpd.conf file.

This is a preview of HOWTO: determine optimal fastcgi settings for Lighttpd. Read the full post (325 words, 1 image, estimated 1:18 mins reading time)
Tags , , , , , , , , | Permalink | Comment (0)