News for hackers. Stuff that matters.
Re:Reverse Proxy Performance – Varnish vs. Squid (Part 2) by jacquesm on Wednesday September 09, 2009 @09:45AM (#813100)
Have used both varnish and squid on production servers, currently serving up to 500K+ uniques daily using varnish.

Squid is a 'feature complete' proxy, it's got everything and the kitchen sink. Which means that if all you want is a web-facing proxy without those bells and whistles that there is a good chance that varnish is faster (as it was in our case).

But varnish is not suitable for all deployments, and it can take some pretty scary tweaking to get maximum performance out of it.

Re:Reverse Proxy Performance – Varnish vs. Squid (Part 2) by SwellJoe on Wednesday September 09, 2009 @03:51PM (#813862)
Have used both varnish and squid on production servers, currently serving up to 500K+ uniques daily using varnish.

To put this into perspective, this is only a couple hundred requests per second (I'm assuming a "unique" equates to ~40 item requests). Either Squid or Varnish can handle that load with ease from a single box (roughly ten years ago, my previous company built a 550MHz, 512MB, 1x7200 RPM IDE disk Squid-based appliance that was conservatively specced at 70 tps, and adding a second disk pushed it up to 110 tps).

This is what I meant by performance not being the most important factor in most deployments of this type (though it certainly matters a lot; and faster is always better, since it results in better retention, more sales, more page views, etc.).

Re:Reverse Proxy Performance – Varnish vs. Squid (Part 2) by jacquesm on Wednesday September 09, 2009 @05:01PM (#813963)
Correction, we are serving 12K requests per second across several machines. (4 right now, spreading things out over 6 in a little while).

Our users are rather longer on our site than you assume, and a typical page is 50 hits on the varnish caches.

Re:Reverse Proxy Performance – Varnish vs. Squid (Part 2) by SwellJoe on Wednesday September 09, 2009 @05:36PM (#814025)
OK, your uniques are more demanding than most deployments I've seen. So, performance is of significant importance to you, and it would save you some machines to go with Varnish over Squid (which tops out at a few hundred requests per second, maybe as much as a couple thousand depending on type of work and whether it can be served from RAM, due to various limitations in it's poll-based architecture; then again, it looks like Adrian and Robert and Henrik have done quite a bit of work in the 2.7 and 3.1 branches, so it may be faster today).