atom feed19 messages in ru.sysoev.nginxRe: RE: varnish?
FromSent OnAttachments
Ilan BerknerMar 29, 2009 3:59 pm 
Kiril AngovMar 29, 2009 4:56 pm 
Cliff WellsMar 29, 2009 8:29 pm 
Chris ZimmermanMar 29, 2009 9:10 pm 
russlndrApr 12, 2009 8:17 pm 
CryptWizardApr 12, 2009 10:54 pm 
jeff emmingerApr 13, 2009 6:34 am 
russlndrApr 13, 2009 7:04 am 
Barry AbrahamsonApr 14, 2009 8:59 am 
Victor IggyApr 14, 2009 3:55 pm 
Barry AbrahamsonApr 14, 2009 7:12 pm 
Floren MunteanuApr 14, 2009 8:39 pm 
Victor IggyApr 15, 2009 10:43 am 
Barry AbrahamsonApr 15, 2009 12:14 pm 
zepolenApr 15, 2009 5:58 pm 
Phillip B OldhamApr 16, 2009 12:20 am 
Barry AbrahamsonApr 16, 2009 7:47 am 
Barry AbrahamsonApr 16, 2009 7:52 am 
zepolenApr 17, 2009 1:59 pm 
Subject:Re: RE: varnish?
From:russlndr (ngin@nginx.us)
Date:Apr 12, 2009 8:17:11 pm
List:ru.sysoev.nginx

My company is a heavy user of varnish cache since 2006. We have 6 varnish
servers with 550 GB of RAM caching static pictures for our community. At peak
each server is handling 40k active connections per second.

If you only have one server you should use a dedicated static server and let the
file system cache(linux caches last read data in ram), but it won't scale beyond
that server. But I assume you have many GBs of mp3s and need more than one
cache. Our setup have pools of varnish servers delivering photos from RAM, and
we distribute traffic between the varnishes by hash method so one server only
serve his part of the photos and caches them in memory.

Varnish is also a very hardware friendly software. It makes smokeping look nice.
:)

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,615,1007#msg-1007