Question about varnish memory usage

[Per Buer]

Hi Adam.


On Wed, Sep 17, 2014 at 7:58 PM, Adam Schumacher <
adam.schumacher at flightaware.com> wrote:

> The varnishd process
> grows by about 1M a second until all the physical and virtual memory is
> filled, and then predictably, causes the box to crash.  We only have 6G of
> malloc allocated (and confirmed with SMA.s0.g_bytes 6441093251), and
> n_object 981470
>

It seems you are using Transient storage. Transient is usually uncapped.
You can cap Transient but you should probably figure out why Varnish is
using Transient storage. Usually it will allocate Transient if
1) The objects TTL < 10s
2) Failed to allocate storage

As a hotfix I would cap Transient at, say, 2G. "varnishd -s
Transient=malloc,2G". You can probably up your main storage quite a bit
with this in place.

-- 
*Per Buer*
CTO | Varnish Software AS
Cell: +47 95839117
We Make Websites Fly!
www.varnish-software.com
[image: Register now]
<http://info.varnish-software.com/varnish-summits-autumn-2014-registration>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20140918/7c1ecb1c/attachment-0001.html>