Trying it out and boost seems to not work when using Pressflow
http://fourkitchens.com/pressflow-makes-drupal-scale

CommentFileSizeAuthor
#2 boost-530772.patch800 bytesmikeytown2

Comments

omega8cc’s picture

Now testing different setups based on Pressflow + Ncache + Redis and Cache (not cacherouter) + Boost etc. etc.
Will report some results (and workarounds) soon, since we are moving all our 6.x to Pressflow as a core and we need Boost also.

~Grace

mikeytown2’s picture

Status: Active » Needs review
StatusFileSize
new800 bytes

Error has to do with drupal_set_header(). Most of the // Output buffering callback code section should probably be rewritten. Has to do with array keys and values. I think the quick fix is to use drupal_get_headers() as that gives the correct info in pressflow.

mikeytown2’s picture

Status: Needs review » Fixed

committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

chrism2671’s picture

Have you tried using Varnish instead? That is one of the main selling points of pressflow.

mikeytown2’s picture

chrism2671’s picture

Although I know everybody's mileage might vary, I do believe that if you are using Boost this negates need for Varnish in most situations (I have tested and used both in production environments).

The fastest production configuration I have found so far is:

*Well configured MySQL with my-huge.cnf + double size query cache.
*Pressflow
*memcache
*Nginx - configured to serve static files bypassing PHP + setting expire headers.
*PHP Fast-CGI
*Varnish
*APC + php.stat

Varnish is good for keepings things on the edge. I bet that xcache will be better than APC (as APC does not support fast-cgi efficiently) for PHP 5.2.