Re: varnish consuming too much memory?
On 12.03.2008, at 19:59, Poul-Henning Kamp wrote: i'm wondering how varnish determines how much memory it should consume... It uses all memory it can for caching. - is there a way to limit it? i'd like to assign the 4 varnishes running on this box 3 GB each and leave 4GB for linux disk/nfs cache - what effect has the size of the VARNISH_STORAGE_SIZE? is this cache persistent? when are objects moved from memory to disk? thanks jodok -- 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. -- "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
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: Caching issue
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > "Poul-Henning Kamp" <[EMAIL PROTECTED]> writes: > > Is this FAQ fodder ? > Yes, I'll stick it in the wiki. I added a FAQ entry which links to a separate page on the subject: http://varnish.projects.linpro.no/wiki/FAQ/Compression DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
Re: SSL support
Audun Ytterdal <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav wrote: > > That was a wishlist item, not a promised feature. However, Varnish 2.0 > > supports Vary, so if can enable compression on your backend, it will > > "just work" - but DO NOT UNDER ANY CIRCUMSTANCES use the sample > > configuration at the top of Apache's mod_deflate documentation, as it > > will effectively make every compressable document uncacheable. > > You mean > > "AddOutputFilterByType DEFLATE text/html text/plain text/xml" > > Why will that make documents uncacheable? No, that part is fine. I was referring to the "Compress everything except images" example right below it. > Would be sad for non-gzipable browser, but that would be fixed by > > "Header append Vary User-Agent" Absolutely not. This will force Varnish to cache a separate copy of the document for every single User-Agent string it encounters. Browsers that do not support gzip or deflate do not need special treatment: they do not send Accept-Encoding: and will therefore get an uncompressed version of the page. The only browsers that advertise gzip / deflate support but do not actually support it (and therefore need the BrowserMatch rules) are early versions of Netscape 4. According to thecounter.com's December 2007 statistics, Netscape 4's market share is 0.00067 - less than one in one thousand. DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no ___ varnish-dev mailing list varnish-dev@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-dev
