pressflow

Currently using Drupal 6 / Pressflow on Apache with Google Analytics installed. We have Varnish 2.1.5 running on port 80 in front of Apache.

In the attached Varnish VCL (based on Lullabot's example - http://www.lullabot.com/articles/varnish-multiple-web-servers-drupal), I have (probably redundant) regex filtering Google Analytics cookies, as well as a general 'remove all cookies except sessions' rule in sub vcl_recv.

in our environment even though we have varnish (frontend) w/ apache (backend) somehow logged-in users are able to bring apache to it's knees, it probably have something to do with following:

    // do not serve cached pages for logged in users
    if (req.http.Cookie ~ "SESS[a-f|0-9]+") {
            return (pass);
    }

so I was thinking if it's possible to do following:

1. have pressflow to give out different cookie to a user based on their role.

Which is faster? Which scales better for large sites with a lot of data and traffic? If Pressflow 6 is faster, is the difference significant enough to consider building a new site with it? I've heard that D7 was slower initially, but there have been improvements more recently that closed the gap.

Hola, nuevamente tengo una alta carga en mi sitio y veo demasiados procesos en mi servidor. Aunque he activado la opción cache, hay momentos de mucho tráfico y luego aparece en rojo http, cpanel, sql, etc, y finalmente el mensaje de Apache y el colapso del servidor. Me recomendaron Pressflow y Varnish. Mis dudas son: ¿Puedo migrar mis 20 mil nodos de Drupal 7 a PressFlow, que módulo o herramienta uso? ¿Sólo necesito bajar Pressflow y hacer correr el server o debo instalar Varnish en mi servidor? ¿Es cierto que esas herramientas impiden usar el contador de hits de mi sitio y algunas vistas?

So we use page level caching on our Pressflow 6 multisite installation and some of the sites use a module for IP based role assignment.

There is an issue with using page caching and IP based role assignment in which a user will get a cached page from Varnish despite having an IP that will give them an authenticated role.

I would like to know your thoughts on Drupal and its performance, and especially how to improve it.

We currently use a system based on Drupal 6.22 Project Mercury (Pressflow, Varnish, APC ...) specially designed for heavy traffic. And we have installed more 50 modules like (Views, CCK, Panel, VBO, Rules, Workflow, UberCart, Solr…)

But our production server is a virtual environment with 4 CPUs and 8 GB of Ram, which is really huge for a single site. During our peak traffic, we have over 1,800 visits and more than 50 connected users for one day.

Hi folks,

I am pretty new to the quickstart camp, but so far I like it a lot. I was curious though if anyone has tried integrating pressflow into the quickstart VM? I wanted to see whether the integration of Varnish specifically caused any problems with the use of quickstart and the debugging tools? Also has anyone tried utilizing drush for installing the pressflow instance on quickstart? Any feedback would be welcomed.

Thanks,
Mitch

AFAICT Pressflow 7 is almost exactly the same as Drupal 7 except for these two small patches:
https://github.com/pressflow/7/commit/fa91b2fc80741cb8c42c2db618f0ef0ad8...
https://github.com/pressflow/7/commit/6cb28bfd8f5493be6c606856662d5e7d4d...

Am I missing something?

Currently fixing various notices and I find this query to be very useful in phpmyadmin. Be sure to have "Full Texts" selected under options.

This is what I use on the dev box in settings.php; makes errors very verbose and enables dblog if it is disabled.
<?php
// Show Errors in output
ini_set('display_errors', '1');
// Report all php errors.

Since having attended DrupalCon Chicago (and really well before) we have tried to absorb as much as we could from the advice of the performance community and implement it.

We haven't yet implemented Varnish/memcache/apc..., but we would like to take this (varnish) as our next step. Memory is a bit of a concern for us, we have a handful of services all running on one 8GB machine with a fair amount of daily traffic. I aplogize for the loads of data ahead, but i figured better to write too much rather than not enough.

We are primarily concerned with,