3 ms·
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
by SwellJoe 17y ago
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.).
- jacquesm 17y agoCorrection, 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.
- SwellJoe 17y agoOK, 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).