Re: Memory usage

rily any value in keeping it in physical memory; if no-one ever requests it again, then it makes sense for it to end up in swap... regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: Memory usage

other system processes that have now been shunted out to swap. Once again, `top` VIRT versus RES will give you a good clue regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: Time to replace the hit ratio with something more intuitive?

518.81 1858.98 Client requests received > 390022582 1471.82 1799.15 Cache hits > 1549 0.00 0.01 Cache hits for pass > 905363722.0041.76 Cache misses > > > Now it's up to you, what do you think about this? +1 re

RE: Varnish virtual memory usage

Can you paste your VCL please? Do you use the purge_url function in it? regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > I don't remember how long it took exactly, but it filled up rather > quickly. Probably a couple of hours. I also noticed th

Re: Varnish, long lived cache and purge on change

ad you might otherwise experience, and keep response times low and page freshness high. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: Memory spreading, then stop responding

> Darryl Dixon - Winterhouse Consulting wrote: >>> >>> Can anyone suggest why varnish is using more memory than it's >>> allocated, >>> and why varnishlog would stop returning any output? Varnishlog was >>> writing to disk, so I can

Re: Memory spreading, then stop responding

isk, so I can probably extract the end of that, if it's of > use. > Hi Rob, There have been a few threads about this now on this mailing list. Probably it relates to the use of purge_url in your VCL. Are you using this function at all? regards, Darryl Dixon Winterhouse Consu

Re: hit for pass problems (was: Problems getting Varnish to cache certain things)

n the above TTL value). The problem is the call to 'pass'. You must not do this in vcl_fetch if you want Varnish to be able to cache the item. Instead, restart the request with 'restart'. Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com __

Re: vcl_error restart

some ideas anyway. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > I'm trying to setup varnish so that it will try one backend and then > if there's an error (for example - the backend isn't up at all - not > even throwing 500 errors),

Re: Problems getting Varnish to cache certain things

> In message > <41184.118.93.77.92.1244834146.squir...@services.directender.co.nz>, > "Darryl Dixon - Winterhouse Consulting" writes: >>Hi Anders, >> >>If you perform certain actions in vcl_hit, Varnish will mark the object >> as >>a 

Re: varnish storage tuning

> ]] "Darryl Dixon - Winterhouse Consulting" > > | My testing showed that with purge_url in the VCL, a 'purge record' was > | created every time the rule was struck, and that record never seemed to > be > | removed, which meant that memory grew without bou

Re: Problems getting Varnish to cache certain things

#x27; inside vcl_hit or vcl_fetch. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > Hi, > > I had a situation where some cache servers would cache a URL, and others > would not. The strange thing is, if I restarted Varnish on the servers > t

Re: varnish storage tuning

item, then definitely you don't need to restart. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > Does restart cause the backend to be queried for the page again? I'd > prefer > if a purge did not re-fetch the URL from the backend as this ca

Re: varnish storage tuning

nstead, in vcl_hit, if the object should be purged, set obj.ttl to 0 and then restart the request. This solved the problem for me. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > We're using Varnish and finding that Linux runs the OOM killer on the

Re: Varnish 2.0.3 consuming excessive memory

...] Where, if anywhere, is exp_heap pruned for entries like this? I couldn't quite make sense of exp_timer() to be certain of under what conditions it actually removes things from this heap - it looks like that function is mainly concerned with items expiring from the Expires

Re: Varnish 2.0.3 consuming excessive memory

that exact behaviour (items would no longer be > | cached by varnish) so I swapped it for purge_url... > > You can try setting obj.ttl = 0s and then restart in vcl_hit. I believe > that should work. > Thanks Tollef - I will try this today and report back. r

Re: Varnish 2.0.3 consuming excessive memory

; -s file,"/tmp/storage",600M > > makes it using about 500M RAM (the RES column in top after 5 days of > uptime) > and happily coexist with zope ;-) > > > > maybe this helps you too. > Hi Harald, That is a very interesti

Re: Varnish 2.0.3 consuming excessive memory

Hi DES, > "Darryl Dixon - Winterhouse Consulting" > writes: >> +if (req.http.Pragma ~ ".*no-cache.*" || req.http.Cache-Control ~ >> ".*no-cache.*") { >> +purge_url(regsub(req.url, "[?].*$", ".*$")); >>

Re: Varnish 2.0.3 consuming excessive memory

consistent, continuous upwards trend in terms of memory usage... regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com >> Not that I have an answer, but I'd be curious to see the differences >> in 'pmap -x ' output for the different chil

Re: Varnish 2.0.3 consuming excessive memory

- - rw---[ stack ] ff608192 - - - -[ anon ] -- -- -- -- total kB 3121808 - - - -- Both processes have been running for the same amount of time - 1day 17h

Re: Varnish 2.0.3 consuming excessive memory

nd would cause it to consume and hold on to large amounts of memory? regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Varnish 2.0.3 consuming excessive memory

vcl.syntax changes, and the introduction of request restarts under certain limited scenarios. Can anyone shed some light? regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc

Re: Articles regarding Varnish, VCL and ESI

r me, as I have been thinking about using Varnish's ESI support for a new project I am working on. Currently my strategy for low-overhead dynamic pages revolves around just-in-time ajax. I am definitely inspired now to give it a crack in ESI instead. Thank you very much

Re: Logged-in users

the use-case. Miles: FWIW, the CacheFu product for Plone may assist you to maximise the caching potential of your site without too many custom tweaks to your Varnish rules. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > Another approach is to simply us

Re: want to allow or deny an URL based on a timestamp

d. In this way, the internals of the application are hidden from Varnish as much as possible and localised inside the application itself. Hope this helps. regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com > Nearly every modern webserver has optimized fi

Re: Strategy for large cache sets

ethernet? Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: Varnish and hot linking

sures that the current request will get a fresh copy from the backend, but during the processing of that request, the fresh copy will be 'insert'-ed into the cache during vcl_fetch, and so subsequent requests which hit the 'lookup' in vcl_recv will see the prev

Re: Reloading default.vcl

ue-name > > if you want to get rid of it. > It is pretty easy to automate this all with expect(1) as well, if an 'automated' reload solution is required :) regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: cache files pass php

g is insert-ed into the cache or pass-ed onwards) Hope this helps, regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: Varnish Questions

resented there is probably not correct for your current version). > Thanks for any help someone can give. You're welcome ;) regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhouseconsulting.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: honoring browser reload request

then in vcl_recv we do similar to you: Bother, of course I meant: ..and then in *vcl_hit* we do similar to you... :) > /* Honour Cache-Control: and Pragma: ... */ > if (req.http.Pragma ~ ".*no-cache.*" || req.http.Cache-Control ~ > ".*no-cache.*") { >

Re: honoring browser reload request

exp and req.url could contain some special char (could it?). We tried with purge_url but it was just too hard and didn't want to do what we expected. We've had good results with our configuration above. Hope this helps, regards, Darryl Dixon Winterhouse Consulting Ltd http://www.winterhou