Re: varnish consuming too much memory?
Hi Jodok Please take a look at http://varnish.projects.linpro.no/wiki/ArchitectNotes It should give you a pretty clear idea about the design choices that the varnish team have made. Cheers Dave On 13/03/2008, at 9:27 PM, Jodok Batlogg wrote: can you elaborate or point me to some documentation? is this cache persistent? when are objects moved from memory to disk? No. Whenever the kernel VM subsystem decide it should happen. so it is a kind of home-made swap memory for varnish? thanks jodok ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
Re: varnish consuming too much memory?
On 13.03.2008, at 11:47, Dave Cheney wrote: Hi Jodok Please take a look at http://varnish.projects.linpro.no/wiki/ArchitectNotes It should give you a pretty clear idea about the design choices that the varnish team have made. i've read that document beforehand - but i don't get the point why it should be impossible to limit system resources? jodok Cheers Dave On 13/03/2008, at 9:27 PM, Jodok Batlogg wrote: can you elaborate or point me to some documentation? is this cache persistent? when are objects moved from memory to disk? No. Whenever the kernel VM subsystem decide it should happen. so it is a kind of home-made swap memory for varnish? thanks jodok -- Beautiful is better than ugly. -- The Zen of Python, by Tim Peters Jodok Batlogg, Lovely Systems GmbH Schmelzhütterstraße 26a, 6850 Dornbirn, Austria mobile: +43 676 5683591, phone: +43 5572 908060 ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
Re: varnish consuming too much memory?
On 13.03.2008, at 15:43, Ask Bjørn Hansen wrote: On Mar 13, 2008, at 3:27, Jodok Batlogg wrote: the different sites are running under different users. i'd like to share the resources fair between them. If your platform supports virtualization then you can split up your system into N virtual boxes to limit how much real memory varnish uses for each... well - if you're serving 500mbit/s you don't want a virtualized system... probably i really need to create a more complicated vcl that allows to run all applications within the same cache space. but still it's open how it is possible to reserve some GB of RAM for cache memory... or is it really true that i need dedicated boxes for caching only? jodok - ask -- http://develooper.com/ - http://askask.com/ -- Beautiful is better than ugly. -- The Zen of Python, by Tim Peters Jodok Batlogg, Lovely Systems GmbH Schmelzhütterstraße 26a, 6850 Dornbirn, Austria mobile: +43 676 5683591, phone: +43 5572 908060 ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
varnish consuming too much memory?
hi, i'm wondering how varnish determines how much memory it should consume... we're running multiple varnishes on one box and now and then one instance starts to use more and more memory. right now it's using 65% out of 16GB ram, which is pretty much :) varnishlog shows that pretty much traffic is going on :) varnishhist shows that the requests are beeing served really fast varnishtop shows: the following: list length 569 hu 4537.38 VCL_retur deliver 2655.35 TxProtoco HTTP/1.1 2397.58 RxProtoco HTTP/1.0 2397.58 RxHeader Host: www.zoomer.de 2397.58 RxHeader Connection: close 2397.58 VCL_call recv 2397.58 VCL_retur lookup 2397.58 VCL_call hash 2397.58 VCL_retur hash 2397.58 VCL_call deliver 2397.58 TxHeader Via: 1.1 varnish 2397.58 TxHeader Connection: close 2397.58 SessionCl Connection: close 2378.81 RxRequest GET 2261.07 TxHeader Server: nginx/0.5.35 2261.07 TxHeader Keep-Alive: timeout=20 2252.21 TxStatus 200 2245.30 TxHeader X-Powered-By: Zope (www.zope.org), Python (www.python.org ) 2236.44 TxRespons Ok 2139.80 VCL_call hit 1450.22 RxHeader Accept: */* 1028.78 TxHeader Content-Type: text/html;charset=utf-8 826.47 RxHeader Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 820.48 RxHeader Accept-Encoding: gzip,deflate 796.95 RxHeader User-Agent: Wget/1.10.2 796.95 RxHeader Authorization: Basic aHVtYm9sZHQ6QWxleDA3 737.62 RxHeader Accept-Encoding: gzip, deflate 720.28 RxHeader Accept-Language: de-de,de;q=0.8,en- us;q=0.5,en;q=0.3 685.15 RxHeader Cookie: uid=5BbkCkfYHlkLGChJBTgCAg== 614.14 RxHeader User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.1 585.94 RxHeader Accept: text/xml,application/xml,application/xhtml +xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/ 484.43 TxHeader Content-Type: text/xml;charset=utf-8 480.47 RxURL /xml/generic/humboldt/top1.xml 480.47 Hit 350226425 480.47 Length1555 480.47 TxHeader Last-Modified: Wed, 12 Mar 2008 18:16:06 GMT any idea? jodok -- Beautiful is better than ugly. -- The Zen of Python, by Tim Peters Jodok Batlogg, Lovely Systems GmbH Schmelzhütterstraße 26a, 6850 Dornbirn, Austria mobile: +43 676 5683591, phone: +43 5572 908060 smime.p7s Description: S/MIME cryptographic signature ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
Re: varnish consuming too much memory?
i'm wondering how varnish determines how much memory it should consume... It uses all memory it can for caching. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
