Memory utilisation gradually increasing

[FULLER, David]

Thanks Dridi,

After further investigation I found that we do have a python/cron job running that checks for backend changes and if so does a vcl.load.   This has resulted in a growing number of VCLs being loaded, as you suspected.  After a redeploying the Varnish container this morning and then monitoring varnishadm we have gone from around 30 VCLs loaded to over 200 in a few hours.  Is there a way to limit the number of VCLs that can be loaded, with older ones being dropped as new ones are loaded?



On 28/07/2018, 18:57, "Dridi Boukelmoune" <dridi at varni.sh> wrote:

    On Fri, Jul 27, 2018 at 4:41 PM, FULLER, David <FULLERD at parliament.uk> wrote:
    > Thanks, we have 1 active VCL and around 35 available (of these 3 are auto/warm and the remainder cold/cold).  The containers running Varnish had to be rebuilt a couple of hours ago, so I'll check varnishadm again on Monday to see whether the numbers have increased.  Are the cold/cold VCLs considered loaded in terms of memory usage?

    Yes, cold VCLs are considered loaded in terms of memory usage,
    but in a cold state.

    It means that they have a lower footprint, but an overhead still
    exists. To lower the footprint, varnishd and (well-behaved) VMODs
    release any resources that can be acquired again once the VCL is
    warmed up prior its use. Just telling varnish to `vcl.use` a cold VCL
    will automatically go through the warm up phase, and set the VCL as
    active once it reaches the warm state.

    Dridi



UK Parliament Disclaimer: This e-mail is confidential to the intended recipient. If you have received it in error, please notify the sender and delete it from your system. Any unauthorised use, disclosure, or copying is not permitted. This e-mail has been checked for viruses, but no liability is accepted for any damage caused by any virus transmitted by this e-mail. This e-mail address is not secure, is not encrypted and should not be used for sensitive data.