Hi,
is it possible to see your named.conf
what is the methodology of the test? is it for authoritative queries?
recursive? or both? at the same time?
my patch for the port is the same as yours...
thanks!
===============
.if ${ARCH} == "amd64"
ARCH=x86_64
.endif
--- On Thu, 12/11/08, Dmitry Rybin <[EMAIL PROTECTED]> wrote:
> From: Dmitry Rybin <[EMAIL PROTECTED]>
> Subject: Re: dnsperf and BIND memory consumption
> To: "JINMEI Tatuya / 神明達哉" <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL
> PROTECTED]>
> Date: Thursday, December 11, 2008, 1:50 AM
> JINMEI Tatuya / 神明達哉 wrote:
> > At Tue, 09 Dec 2008 18:05:27 +0300,
> > Dmitry Rybin <[EMAIL PROTECTED]> wrote:
> >
> >> I test patch, add to bind95/Makefile
> >> .if (${ARCH} == "amd64")
> >> ARCH= x86_64
> >> .endif
> >
> > Future versions of BIND9 will support amd64 in its
> configure script to
> > workaround the FreeBSD port for amd64.
> >
> > Regarding the memory leak, I believe it's already
> solved in 9.5.1rc1
> > (even with threads and without atomic).
>
> I just make port bind 9.5.1rc1. It has same problem with
> memory leak.
> It grows from 670M on startup, to 1,4Gb after 20 minutes of
> work.
>
> grep x86 work/bind-9.5.1rc1/config.log
> ISC_ARCH_DIR='x86_32'
> build='x86_64-portbld-freebsd7.0'
> build_alias='x86_64-portbld-freebsd7.0'
> build_cpu='x86_64'
> host='x86_64-portbld-freebsd7.0'
> host_cpu='x86_64'
>
> _______________________________________________
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
