Drupal Profiling with XHProf on Ubuntu 11.10 + Memcached and Varnish

  1. Install memcached, varnish, and xhprof

    sudo apt-get install memcached
    sudo apt-get install php5-memcached
    sudo apt-get install varnish
    sudo pecl install php-xhprof

  2. Install xhprof front-end

    cd /var/www
    git clone

  3. Configure Apache and Varnish ports

    sudo vim /etc/apache2/ports.conf ; // Change 80 to 8080
    sudo vim /etc/apache2/sites-available/default // Change 80 to 8080
    sudo vim /etc/default/varnish // Change 6081 to 80

  4. [Re]start services

Set Drupal cache and aggregation settings in settings.php

Drupal 6:

$conf['preprocess_css'] = 0;
$conf['preprocess_js'] = 0;
$conf['cache'] = 0;



Set Drupal files directory path in settings.php

In Drupal 6 settings.php:

$conf['file_directory_path'] = 'sites/';

In Drupal 7 settings.php:

$conf['file_public_path'] = 'sites/';
$conf['file_private_path'] = '/var/_private-web-files/';


New system setup notes: Ubuntu 11.10 on Toshiba Satellite A505-S6992

on a toshiba a505-s6992


To Do List After installing Ubuntu 11.10 aka Oneiric Ocelot

15 Things I Did After Installing New Ubuntu 11.10 Oneiric Ocelot


to get external monitor to work, had to install latest nvidia drivers:

Looking Forward to Development in Drupal (7 and 8) with Git, Drush, and ...Eclipse?

Beginning my Drupal 7 development today with a git clone of drupal, and setting up my local development environment with MAMP and Drush, I am glad to be started with Drupal 7 and excited to have that 8.x branch enticing me on, too.  I know git will help ease the pain of site and multi-site maintenance against the latest Drupal releases, and Drush (4.x) will help blast through build, deployment, and management chores.

Drupal Site Upgrades with Drush in Git/Eclipse Workflow

I've got a Drupal 6.14 installation recently initialized as a Git repo that I now need to upgrade (from Drupal core 6.14 to 6.19 and to the latest versions of several contributed modules.  To safely upgrade this site I'll perform the upgrades locally and make sure they don't break any of the functionality - especially in the features from custom modules which may have been written against these now outdated versions of some important modules.  So the idea is to create a branch from the current code to a new line of development for these upgrades.  I'm familiar with SVN branch

Syndicate content