Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm thinking about the architecture for a new Webserver. Would having Varnish as a cache in front of Nginx as a reverse-proxy and serving static files in front of apache for all heavy lifting be a good idea?

I'm going to run php and ruby on rails applications.

Will there be too much overhead passing php requests to apache through two other processes?

Thanks a lot!

share|improve this question
add comment

7 Answers

up vote 7 down vote accepted

Yeah, it's valid. My personal approach would be to use Varnish up front and use VCL to split the traffic between static NGINX requests and your heavy lifting (whether that be Apache or Passenger or... it doesn't matter). This is especially true if it is on the same machine as you don't need the extra overhead. It doesn't necessarily buy you anything.

share|improve this answer
    
yeah this is a pretty good idea, since varnish should be pretty fast for this –  Zoran Zaric May 20 '10 at 18:23
add comment

Varnish doesn't (yet) support gzip compression, so it might be an idea to swap it around with nginx in front to compress what varnish sends back. Since varnish and nginx don't fight for the same resources (nginx uses CPU for gzip compression, while varnish uses memory) they should run smoothly on the same machine.

Varnish now supports gzip compression, so unless you need SSL termination (as suggested in the comments), I would suggest putting varnish directly in contact with the Internet.

For http:

(internet) --> (varnish, gzip, caching, esi) --> (application)

For https:

(internet) --> (nginx, ssl)--> (varnish, gzip, caching, esi) --> (application)

If you want apache in there too (for the ubiquitous mod_foobar support), I'd put it between varnish and the application

Update: Updated to include gzip support in varnish 3.0. Added ssl / esi as suggested in comments

share|improve this answer
    
If whatever is serving content to varnish encodes it in gzip, then varnish will pass it on gzipped without complaining: varnish-cache.org/wiki/FAQ/Compression The only thing varnish doesn't do is take content which is uncompressed from the uncached application and reserve it compressed. Is this your understanding as well? –  ewalk Jun 15 '10 at 17:48
    
The only time you run nginx in front of varnish is when you are using ESI. Since you cannot do ESI assembly from compressed pages, and Varnish will not compress an assembled page, Nginx is placed in front of Varnish to provide that compression. If the origin serves the content compressed, Varnish will pass that data to the client in compressed form. –  user6738237482 Jun 15 '10 at 18:48
    
Yeah, ESI is one of the reasons why I'd recommend this configuration, but I guess that if your backend compresses and you don't use ESI, you could dispense with nginx, since I believe varnish can handle quite a lot of traffic without breaking a sweat. –  mogsie Jul 7 '10 at 20:34
    
@user6738237482, nginx suport SSL termination, Varnish does not. In fact, being in front of something like varnish or Apache is exactly what nginx was originally designed for, as a fast, lightweight proxy server. –  rmalayter Apr 18 '11 at 13:03
add comment

The amount of overhead shouldn't be significant. I'm assuming part of the reason you want to have these two tiers is for scalability; in which case you would most likely see, relative to apache, that varnish and nginx aren't working very hard.

If you all three tiers on one machine, there should be less of a performance impact before you reach the capacity of the server itself.

As an alternative, why not varnish + nginx with passenger? I've used this setup in the past and nginx using passenger is relatively light, and ran pretty well. Might be worth thinking about if you're not married to apache running your rails stack.

share|improve this answer
    
yeah i might switch from apache to nginx for rails, but giving customers the ability to use .htaccess files is a + for apache, for php at least. –  Zoran Zaric May 20 '10 at 18:22
add comment

I am the sys admin for a startup ecommerce platform. We use varnish+nginx in front of our PHP/apache stack and it has worked wonders.

We have a high memory use application and the app was using around 15-20gigs of RAM per webnode and once we put varnish in front it is now around 8gig of RAM per node. They have never spiked.

So I highly recommend it.

share|improve this answer
3  
You know varnish doesn't talk ssl right? –  Mike Jun 15 '10 at 19:23
add comment

I'm running Drupal, with boost module on an Apache+PHP+MySQL server, but in front of them I'm using Nginx with gzip-static feature on, and using the results of boost to serve the users.

And on the top of all of that I'm using varnish, all on the same PC, I'm having good results.

I'm also using Nginx to tweak the headers that Drupal does not do very well for cache.

share|improve this answer
add comment

It isn't a good idea unless you need something like ESI. Nginx has it's own caching system that performs better.

share|improve this answer
add comment

Apache can be used to SSL terminate (decrypt), check http://noosfero.org/Development/Varnish#SSL

share|improve this answer
1  
Please avoid posting links as answers, as your answer is likely to lose all meaning when it is affected by linkrot. Please consider editing your answer and including relevant parts from the link you have supplied in your answer. By all means leave the link in place as a reference. –  Bryan Jul 4 '13 at 22:07
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.