varnish

I'd posted this @ http://lists.drupal.org/pipermail/support/2011-November/019837.html, and got a msg that that list, too, is the 'wrong place', and that this is a better choice. Feeling a bit like a ping pong ball ... Anyways:

I've been considering putting Varnish3 in front of Drupal7.

I've scoured scads of snippets of inconsistent/incomplete/outdated
information from the HighPerformance group, the FourKitchens wiki, the
Varnish wiki, the Drupal Varnish module threads, countless blogs,
BadCamp presentations, various mailing lists, etc.

Buenas,
en la empresa tenemos una instancia de Amazon de las grandes y nos lleva el sitio sobrada.
El problema es que lanzamos boletines y a lo largo de la semana solemos tener un par de día con un pico bastante fuerte. Para solventarlo hemos decidido, como primera medida de choque, poner Varnish.
El caso es que lo monté y lo configuré, pero, pese a que el servidor ahora responde mucho mejor a los picos, creo que me cachea poco, me gustaría que cacheara un poco mas para quitarle aun mayor parte al Apache.

(Referred from http://drupal.org/node/1255892)

I have been working on two development servers to try out a concept:

Server 1.
varnish -> apache > drupal, and

Server 2
nginx -> apache > drupal, with
nginx -> (jpg, txt).

I have read all good things about running nginx with no modules to server Static Content (images, text files, etc) and it seems to work very well on server 2.

Both development servers are working very well. What I would now like to try is to combine the benefits of both but I do not know which is the preferred setup?

We are in the process of getting ready to release a game in the next few months, most of all the back-end is handled by drupal and some custom plugins, but we are now looking to move towards the cloud and making sure drupal and the db can handle the traffic.

I have started down the road of googling all over the and of course ran into project mercury / panthon / press flow etc..

Exove Ltd is developing a new module, integrating Varnish into Drupal in a way that allows caching not only anonymous users' content, but authenticated users' content as well.

The basic idea behind the module is to generate cacheable anonymous versions from any page with cacheable content, leaving placeholders in place of user specific content, and to serve those versions to all users. Any user-specific content is then replaced with AJAX for all authenticated users.

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,

(moved from http://groups.drupal.org/node/148319)

our current web stack is an all IPv4, DIY implementation of,

    nginx
        multiple listeners on IPv4:80, IPv4:443
        proxypass to varnish-cache on 127.0.0.1:9000
      |
      |
    varnish-cache
        listener on 127.0.0.1:9000
        filter/pass to 'faux-CDN' on Apache2
            'img' -> 127.0.0.1:12003
            'css' -> 127.0.0.1:12002
            'js'  -> 127.0.0.1:12001
            '...' -> 127.0.0.1:12000
      |
      |
    apache2/mod_php,mod_deflate +
    Pressflow6/memcached(cache_inc/session_inc/lock_inc)
        listeners/vhosts on 127.0.0.1:1200{0,1,2,3}

Hi,
I successfully update my server from Ubuntu 9.04 & Mercury 1 to Ubuntu 10 LTS & Mercury 1.1,
but I notice that on the new Varnish default.vlc there is no has_js cookie bypass. Is it not useful anymore?

Mercury 1

Mercury 1.1

our current web stack is an all IPv4, DIY implementation of,

	nginx
		multiple listeners on IPv4:80, IPv4:443
		proxypass to varnish-cache on 127.0.0.1:9000
	  |
	  |
	varnish-cache
		listener on 127.0.0.1:9000
		filter/pass to 'faux-CDN' on Apache2
			'img' -> 127.0.0.1:12003
			'css' -> 127.0.0.1:12002
			'js'  -> 127.0.0.1:12001
			'...' -> 127.0.0.1:12000
	  |
	  |
	apache2/mod_php,mod_deflate +
	Pressflow6/memcached(cache_inc/session_inc/lock_inc)
		listeners/vhosts on 127.0.0.1:1200{0,1,2,3}

all works as planned.

I've got an issue with varnish on my mercury server. I have a site that is located outside of /var/www so I setup a new apache vhost for the site that points to it's proper location and configured it to run on port 8080. When I try to visit the site through varnish on port 80 the default site comes up instead of the site i am expecting. When I visit the site on port 8080 it works fine. Is there something I need to do to varnish to make it aware that the site is not in /var/www? Any help would be appreciated.