I recently made a loadtest against through varnish.
First I received a very high response time and found out that varnish was
maxing the maximum nr of threads.
I updated thread_min = 5 and thread_max = 300 and recevied much better resp.
times.
Then I increased the nr of concurrent users and
Using latest varnish from FreeBSD ports (version 1.1.2), is the
following VCL the correct solution to support browser shift-reloads to
get fresh content and actually update the cache?
sub vcl_hit {
if (req.http.Cache-Control ~ no-cache) {
set obj.ttl = 0s;
pass;
}
}
Raising the number of threads will not significantly improve Varnish
concurrency in most cases. I did a test a few months ago using 4 CPUs on
RHEL 4.6 with very high request concurrency and a very low
request-per-connection ratio (i.e., 1:1, no keepalives) and found that the
magic number is about
Hi Folks,
we're currently evaluating varnish using it to cache all sorts of static
content. It mostly works with minimal configuration, but we are
experiencing really strange browser hangs.
First, the site loads without problem. Then, after clicking a bit
around, the browser (tested: firefox
Christian Wiese wrote:
The funny thing is that this seems to be a client thing. When I have a
browser hanging, I can fetch the same file with curl or wget just fine.
This could be due to Varnish having different versions in different
encodings (gzip/deflate/etc). Take a look at the encoding
