Unbound 1.7.3 eats too much memory comparing previous version

ѽ҉ᶬḳ℠ vtol at gmx.net
Tue Jul 10 09:10:06 UTC 2018

> The memory configuration is for the amount that Unbound allocates.  The
> total max amount of memory that Unbound ends up using because of that is
> about double the specified amount (this may differ for different
> implementations of malloc on different systems).  So if you specified
> 100 Mb cache, it'll end up using 200Mb of memory for that.  I have
> reports that it then stabilizes and stops growing, for others.  Add up
> the memory amounts for the caches and x2 is the guess I would make.  In
> reality unbound also needs some memory for system buffers and so on, for
> large TCP (or TLS) deployments that is a considerable amount. So perhaps
> it is that you configured a lot of memory to be used and it is simply
> growing to fill the config amount?
> Best regards, Wouter

Thank you for the feedback. Below is the deployed configuration. Over
the past 12 hours the ram available reported by >>free -m<< decreased
from 1885 to 1854, that is ~ 2.5 MB/hrs

  rrset-roundrobin: yes
  outgoing-num-tcp: 25
  incoming-num-tcp: 25
  do-ip6: no
  so-reuseport: yes
  so-rcvbuf: 4m
  so-sndbuf: 4m
  use-caps-for-id: yes
  qname-minimisation: yes
  harden-below-nxdomain: yes
  key-cache-size: 50m
  key-cache-slabs: 1
  neg-cache-size: 200k
  msg-cache-slabs: 1
  num-queries-per-thread: 50
  rrset-cache-size: 100m
  rrset-cache-slabs: 1
  infra-cache-slabs: 1
  infra-cache-numhosts: 200
  msg-buffer-size: 8192

More information about the Unbound-users mailing list