varnish
Tux, Varnish or Squid? [closed]
In my experience varnish is much faster than squid, but equally importantly it’s much less of a black box than squid is. Varnish gives you access to very detailed logs that are useful when debugging problems. It’s configuration language is also much simpler and much more powerful that squid’s.
Haproxy in front of varnish or the other way round?
I built a similar setup a few years back for a busy web application (only I did it with Squid instead of Varnish), and it worked out well. I would recommend using your first setup (HAProxy -> Varnish) with two modifications: Add a secondary HAProxy server using keepalived and a shared virtual IP Use the … Read more
Configure multiple sites with Varnish
You can support multiple frontend domains this way: backend example1 { .host = “backend.example1.com”; .port = “8080”; } backend example2 { .host = “backend.example2.com”; .port = “8080”; } sub vcl_recv { if (req.http.host == “example1.com”) { #You will need the following line only if your backend has multiple virtual host names set req.http.host = “backend.example1.com”; … Read more
What does Varnish hit-for-pass mean?
A hit_for_pass object is made to optimize the fetch procedure against a backend server. For ordinary cache misses, Varnish will queue all clients requesting the same cache object and send a single request to the backend. This is usually quickest, letting the backend work on a single request instead of swamping it with n requests … Read more
Memcache(d) vs. Varnish for speeding up 3 tier web architecture
Varnish is in front of the webserver; it works as a reverse http proxy that caches. You can use both. Mostly write — Varnish will need to have affected pages purged. This will result in an overhead and little benefit for modified pages. Mostly read — Varnish will probably cover most of it. Similar read … Read more