1) How many servers do you have running Varnish?
30
2) What sort of total load are you having? Mbit/s or hits per second are
preferred metrics. 2gbt per second
3) What sort of site is it? ecommerce
*) Online media
*) Cooperate website (ibm.com or similar)
*) Retail
*) Educational
*)
Sorry for the late reply.
1) About 200 servers
2) Averages 2500 hits/sec over the day, approx 35% hit ratio (which is
awesome for web hosting)
3) Web hosting
4) No
5)
#1 Allow for 304 revalidation of cache content.
#2 There was an earlier reply that mentioned automatic revalidation
for warm
1) One active server. We have another one as hot standby.
2) 50Mbit, 200 requests/second max. Most of the time it's 10Mbit, 40
requests/second which isn't much.
3) Internet touroperator.
4) Nope
5) Automatic refreshing of data without having the endusers have to wait
for the response.
The
1) 15
2) Arround 10k/s results in 500-600Mbit.
3) Social Network website
4) No
5) Large dataset performance improvements, High traffic performance improvements
rr
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
1) ~20 (Mixture of production and development environments, spread
across London, Tokyo and New York)
2) Low figures - 300-500 hits/s at peak. A lot of our backends have
very high latency though (~200ms just to connect to the server), and
are predominantly static content, so caching speeds up
: varnish-misc-boun...@projects.linpro.no
[mailto:varnish-misc-boun...@projects.linpro.no] On Behalf Of Martin Boer
Sent: Tuesday, 2 February 2010 10:23 p.m.
To: Per Andreas Buer
Cc: varnish-misc@projects.linpro.no
Subject: Re: Survey; how do you use Varnish?
1) One active server. We have another one
]] Václav Bílek
| 5)gracefull restart( not in meaning of persistent cache, but in the
| meaning of not flushing all clients and letting them wait for tens of
| seconds till enough threads appear.)
You can tune the thread_pool_add_delay parameter to at least bring the
time down somewhat.
--
Tollef Fog Heen napsal(a):
]] Václav Bílek
| 5)gracefull restart( not in meaning of persistent cache, but in the
| meaning of not flushing all clients and letting them wait for tens of
| seconds till enough threads appear.)
You can tune the thread_pool_add_delay parameter to at least
