About memory leak? Unbound 1.4.22

Unbound
1

Hi,Folks,

I have questions about Unbound 1.4.22

I began to use recently Unbound.
before that i was using ISC-BIND.

Unbound to service in a production environment,
It seems like memory leak as the recursive query increases.
Is high and utilization compared to ISC-BIND.
(but,Unbound and ISC-BIND rr-cache-size configure parameter is different.)

Unbound is easy to memory leak?
Or ,Unbound bugs?
Or , It is proportional to the cache size value ?

Now "Resident set size" is about 4GB.

It does parameter tuning is bad?.....

Best regards

2

Zitat von Techs_Maru <tecabu@gmail.com>:

Hi,Folks,

I have questions about Unbound 1.4.22

I began to use recently Unbound.
before that i was using ISC-BIND.

Unbound to service in a production environment,
It seems like memory leak as the recursive query increases.
Is high and utilization compared to ISC-BIND.
(but,Unbound and ISC-BIND rr-cache-size configure parameter is different.)

Unbound is easy to memory leak?
Or ,Unbound bugs?
Or , It is proportional to the cache size value ?

Now "Resident set size" is about 4GB.

It does parameter tuning is bad?.....

Hello,

have you read http://www.unbound.net/documentation/howto_optimise.html ??

"Due to malloc overhead, the total memory usage is likely to rise to double (or 2.5x) the total cache memory that is entered into the config."

And no, memory leaks are not common in Unbound to my knowledge at least.

Regards

Andreas

3

Hi,

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.

Ales

4

Hi,Andreas,

thank you for reply.

have you read http://www.unbound.net/documentation/howto_optimise.html ??

"Due to malloc overhead, the total memory usage is likely to rise to double
(or 2.5x) the total cache memory that is entered into the config."

And no, memory leaks are not common in Unbound to my knowledge at least.

Yes,I know them.
I have read the document.
But,because I have felt using too many memory by Unbound Process...

I think trying the tuning of parameters of value.
thanks.

best regards.

/// Maru

5

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?

Best regards.

/// Maru

6

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

7

WOW, can you describe why you need such a large setup? (70GB seems a
bit of overkill for 1 node).

8

Well, we could live with much less, I agree. On the other hand there is ~ 1mil. of active clients doing tens of thousands req/s. And we have an excellent cache hit ratio, more than 90%.

9

Hi,

Thank you for showing config data.
It was very useful.

/// Maru