dnsperf and BIND memory consumption

Dmitry Rybin kirgudu at corbina.net
Tue Dec 9 15:05:27 UTC 2008


I test patch, add to bind95/Makefile
.if (${ARCH} == "amd64")
ARCH=           x86_64

uname -m = amd64
/usr/bin/uname -p = amd64
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler

I didn't find any affect, memory leak very quickly with threads support,
and slowly without threads.

FreeBSD xxx 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul  2 14:18:35 MSD
2008     xxx at xxx:/usr/obj/usr/src/sys/H1  amd64

Vinny Abello wrote:

>>> so does this memory leak only occur if
>>> @ISC_ARCH_DIR@ is "noatomic" under FreeBSD amd64?
>>> and not when its "x86_32" ?
>> First off, note that I have no explicit evidence of memory leak.  But
>> *if there is indeed leak in the FreeBSD pthread library*, the key is
>> "noatomic".  With this configuration named will call pthread
>> locks/unlocks much, much heavier, so the problem may be observable
>> more clearly.  named still uses pthread locks Even with x86_32, so it
>> may just be leaking memory more slowly.
>> Again, everything is just a guess and could be wrong.  We should seek
>> advice from someone who knows FreeBSD library well.
> Just out of curiosity, why in theory is this not seen in prior versions of BIND such as 9.4.2-P2 or 9.4.3 on the same FreeBSD 7.0 AMD64 platforms with threading enabled in BIND?

Рыбин Дмитрий
Управление магистральной сети
Отдел Информационных Систем
Руководитель группы АВР
Corbina Telecom
Tel: +7(495) 728-4000

More information about the bind-users mailing list