Hello David,
Have a look at varnishstat ("varnishstat -1 | grep -e g_space -e g_bytes").
When you are passing, varnish is going to consume Transient storage.
--
Guillaume Quintard
On Wed, Jul 25, 2018 at 7:19 AM, FULLER, David <[email protected]>
wrote:
> We currently have an issue with memory utilisation in Varnish 5.2.1, we
> are only using Reverse Proxy not the caching functionality.
>
>
>
> We are running it in an AWS ECS Docker container, with 1GB of memory
> allocated. Memory increases daily by around 8% until it tops out and site
> connectivity problems occur. Redeploying the container resolves the
> problem and the cycle starts again.
>
>
>
> When Varnish starts we have ‘malloc’ set at 100MB, from my understanding
> this setting is only relevant if caching is being used, which in our case
> it isn’t.
>
>
>
> Has anyone seen a similar problem?
>
>
>
> Thanks
>
>
> 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.
>
> _______________________________________________
> varnish-misc mailing list
> [email protected]
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
>
_______________________________________________
varnish-misc mailing list
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
