Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

squid : Optimising Web Delivery -
Varnish :

which one is better to use and why?

share|improve this question

closed as not constructive by MattB, Jim B, Warner, squillman, Chopper3 May 15 '10 at 7:02

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Better for what? – sh-beta May 13 '10 at 16:49
up vote 1 down vote accepted

The answer to this question is: it depends :)

Based in my experience with caching static content, Varnish is much faster when you have few concurrent connections but loses to squid when you have many concurrent connections, but this is only true for the work loads I've tested with my specific data.

There are many variables at stake. The best thing you can do is benchmarking both varnish and squid against your content and in your environment and then choose the one that best suits your needs.

share|improve this answer

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