varnish

I am utilizing the flag module on a site for multiple purposes; bookmarks, likes, favorites etc. Because flags are stored directly into the database I am a bit worried about running down the database. Is it possible to store flags in memcache or similar and then process them on cron?(as the VotingAPI allows). Any suggestions welcome.

Note: I am planing to run Varnish with ESI(loggedin users), memcache, nginx and CDN. Also I considering using Disqus module for comments (to help offload the database).

I'm trying to speed up my website and need some suggestions about what things go together and which typically give you the most performance increase. I need to lower CPU usage and caching seems like the way to go. We really need to decrease CPU because our host (a pretty well respected and expensive VPS) is being overloaded with only 2-3 simultaneous users. I've run Yslow and the developers are working on making the recommended changes there.

Hi,

Can somebody show me an example of config Nginx+Varnish? It is complicated to make them work together?

I use Perusio's Nginx config and I must switch from Boost to Varnish...

Thanks

I am working on a site, which will eventually use both varnish and a CDN and I am going to implement both of these solutions.

What I am unsure about is which one first. The server at the moment can handle the load that it is getting, so my thoughts are which will get the page into the hands of the user quickest.

I am sure that this could be argued either way, but do people have guidelines or weighing factors as to which way round these should be implemented.

Hello

My stack:
- Ubuntu / LAMP
- Drupal 7.14
- Varnish 3.0.2
- HTTP port 8080 / varnishd port 80

varnishd is running in front of backserver.

Basically, X-Varnish-Cache = MISS in header for ALL the pages, not caching anything at all.

I also tested in http://www.isvarnishworking.com , the result confirmed, please see my screenshot below

HTTP header screenshot:

www.isvarnishworking.com test result screenshot:

I've been trying out several VCL files across the web but my problem seems to be a bit different. I have several websites (Rails + PHP) running on my server on Nginx + PHP-FDM on port 80 and I need to setup Varnish for one of my Drupal websites only so I obviously cannot change the port 80 to be used by Varnish as all the other sites will go down as well.
Any Ideas what my VCL file should look like in this case? (PHP-FDM is running on port 9000)

I set up Varnish. But it cached the logged in homepage which I think it's because the ending of logging-in would actually redirect user to the homepage but cookie at that time has not been set yet for Varnish to be aware of and "pass" .

Tell me if I understand it wrong. ( After logged in, I visited other pages, they are not cached as it should not. No page should be cached once user logged in. ( What Pressflow cookie "LOGGED_IN" is for ). What happened to other pages should also happen on homepage but it's not. )

I have used varnish quite a bit on my LAMP stacks and this deff helps quite a bit out for static files to serve up and keeps the load off of apache.

I hear good things about nginx static file caching so is their a need to put varnish up a head of it?

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.