Hi,
see the common part of the config of my resolvers: server: verbosity: 1 statistics-interval: 900 statistics-cumulative: yes extended-statistics: yes num-threads: 16 msg-cache-size: 18G msg-cache-slabs: 16 num-queries-per-thread: 2048 rrset-cache-size: 36G rrset-cache-slabs: 16 infra-cache-slabs: 16 infra-cache-numhosts: 1000000 do-ip6: yes access-control: 0.0.0.0/0 allow access-control: ::0/0 allow logfile: "/var/log/unbound/unbound.log" log-time-ascii: yes hide-identity: yes hide-version: yes version: "" use-caps-for-id: yes prefetch: yes dlv-anchor-file: "dlv.isc.org.key" val-clean-additional: yes val-log-level: 2 key-cache-size: 12G key-cache-slabs: 16 neg-cache-size: 512m local-data: "z0vWaTC0.testdomain.test. IN A 10.0.0.1" include: "/etc/unbound/unbound.conf.d/local_zones" include: "/etc/unbound/unbound.conf.d/forward_zones" python: remote-control: control-enable: yes control-interface: 127.0.0.1 control-port: 953 On Tue, 26 May 2015 11:52:33 +0900, Techs_Maru wrote: > Hi, > > Thank you for teaching me. > >> we are running 1.4.22 for more than a year. Unbound is allowed to use ~70 GiB (and uses) of memory and we never had a problem with memory leaks. The same setup is on eight servers. > Please tell me if that is possible, How about value is rrset-cache-size? and prefetch parameter is on?
_______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
