Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users


> On May 21, 2025, at 3:38 PM, Ben Scott  wrote:
> 
> - Original Message -
>> From: "Philip Prindeville via bind-users" 
>> To: "bind-users" 
>> Sent: Sunday, May 18, 2025 5:20:59 PM
>> Subject: Significant memory usage
> 
>> What I’ve noticed is that at startup I’m using about 33K pages as the VSZ 
>> (per
>> top on x86_64 hardware).
> 
>  VSZ (virtual size) just counts the number of virtual memory pages associated 
> with the process in some way.  That includes RAM, but also memory mapped 
> files, devices, sparse pages that will never be backed by anything, etc.  You 
> need to look at RSS (resident size) to monitor actual RAM usage.
> 
>  The results of "rdnc stats" and/or the "statistics-channels" will provide 
> BIND-specific statistics.  The former can be run without preparation; the 
> latter is a bit friendlier but needs a config change.
> 
> https://kb.isc.org/docs/monitoring-recommendations-for-bind-9
> 
> https://kb.isc.org/docs/aa-00769
> 
> https://kb.isc.org/docs/aa-01123
> 
> — Ben
> 




I’m currently doing an “rndc flush” every hour to stop my system from getting 
exhausted.  I’ll disable that and report back in a few hours.

Also trying to port jemalloc to Openwrt and rebuild Bind against that.  Would 
have done this sooner but there was a Strongswan issue that took precedence.

But for now I’m seeing:

+++ Statistics Dump +++ (1749414883)
++ Incoming Requests ++
  202350 QUERY
  866925 UPDATE
++ Incoming Queries ++
  100752 A
 726 NS
  11 CNAME
3286 SOA
2040 PTR
 287 MX
4243 TXT
   59691 
3938 SRV
1112 NAPTR
   2 DNSKEY
5043 SVCB
   21219 HTTPS
++ Outgoing Rcodes ++
  713834 NOERROR
1146 SERVFAIL
   52791 NXDOMAIN
  25 REFUSED
  288430 YXDOMAIN
++ Outgoing Queries ++
[View: default]
  102499 A
   53762 NS
 281 CNAME
  95 SOA
 266 PTR
 189 MX
1581 TXT
   21112 
 233 SRV
 227 NAPTR
9372 DS
2623 DNSKEY
   17076 HTTPS
[View: _bind]
++ Name Server Statistics ++
 1069275 IPv4 requests received
   24143 requests with EDNS(0) received
  868523 requests with TSIG received
3377 TCP requests received
   2 TCP connection high-water
  25 update requests rejected
 1056226 responses sent
 415 truncated responses sent
   24143 responses with EDNS(0) sent
  868523 responses with TSIG sent
  117485 queries resulted in successful answer
   42841 queries resulted in authoritative answer
  145314 queries resulted in non authoritative answer
   17879 queries resulted in nxrrset
1146 queries resulted in SERVFAIL
   52791 queries resulted in NXDOMAIN
   90820 queries caused recursion
   13049 duplicate queries received
  578470 updates completed
  288430 updates failed
  288430 updates rejected due to prerequisite failure
 105 Recursive clients high-water
  199789 UDP queries received
1809 TCP queries received
   1 COOKIE option received
   1 COOKIE - client only
 199 synthesized a NXDOMAIN response
   2 synthesized a no-data response
1377 queries triggered prefetch
++ Zone Maintenance Statistics ++
   2 IPv4 notifies sent
++ Resolver Statistics ++
[Common]
[View: default]
  209316 IPv4 queries sent
  208247 IPv4 responses received
   14032 NXDOMAIN received
   2 SERVFAIL received
   6 FORMERR received
   6 EDNS(0) query failures
 449 truncated responses received
   66912 query retries
1003 query timeouts
   32195 IPv4 NS address fetches
  30 IPv4 NS address fetch failed
  143548 DNSSEC validation attempted
   91201 DNSSEC validation succeeded
   52343 DNSSEC NX validation succeeded
   4 DNSSEC validation failed
  198192 queries with RTT 10-100ms
   10027 queries with RTT 100-500ms
   8 queries with RTT 500-800ms
  13 queries with RTT 800-1600ms
   7 queries with RTT > 1600ms
   2 bucket size
  69 REFUSED received
  203461 COOKIE send with client cookie only
5849 COOKIE sent with clie

Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users


> On Jun 8, 2025, at 3:07 PM, Philip Prindeville via bind-users 
>  wrote:
> 
> 
> 
>> On May 21, 2025, at 3:38 PM, Ben Scott  wrote:
>> 
>> - Original Message -
>>> From: "Philip Prindeville via bind-users" 
>>> To: "bind-users" 
>>> Sent: Sunday, May 18, 2025 5:20:59 PM
>>> Subject: Significant memory usage
>> 
>>> What I’ve noticed is that at startup I’m using about 33K pages as the VSZ 
>>> (per
>>> top on x86_64 hardware).
>> 
>> VSZ (virtual size) just counts the number of virtual memory pages associated 
>> with the process in some way.  That includes RAM, but also memory mapped 
>> files, devices, sparse pages that will never be backed by anything, etc.  
>> You need to look at RSS (resident size) to monitor actual RAM usage.
>> 
>> The results of "rdnc stats" and/or the "statistics-channels" will provide 
>> BIND-specific statistics.  The former can be run without preparation; the 
>> latter is a bit friendlier but needs a config change.
>> 
>> https://kb.isc.org/docs/monitoring-recommendations-for-bind-9
>> 
>> https://kb.isc.org/docs/aa-00769
>> 
>> https://kb.isc.org/docs/aa-01123
>> 
>> —Ben
> 
> 
> 
> Dumb question… how do you turn on statistics-channel when building bind?  I’m 
> not seeing an option for it in ./configure


Found it by digging around:  —-with-openssl --with-libxml2 —-enable-threads

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users


> On May 21, 2025, at 3:38 PM, Ben Scott  wrote:
> 
> - Original Message -
>> From: "Philip Prindeville via bind-users" 
>> To: "bind-users" 
>> Sent: Sunday, May 18, 2025 5:20:59 PM
>> Subject: Significant memory usage
> 
>> What I’ve noticed is that at startup I’m using about 33K pages as the VSZ 
>> (per
>> top on x86_64 hardware).
> 
>  VSZ (virtual size) just counts the number of virtual memory pages associated 
> with the process in some way.  That includes RAM, but also memory mapped 
> files, devices, sparse pages that will never be backed by anything, etc.  You 
> need to look at RSS (resident size) to monitor actual RAM usage.
> 
>  The results of "rdnc stats" and/or the "statistics-channels" will provide 
> BIND-specific statistics.  The former can be run without preparation; the 
> latter is a bit friendlier but needs a config change.
> 
> https://kb.isc.org/docs/monitoring-recommendations-for-bind-9
> 
> https://kb.isc.org/docs/aa-00769
> 
> https://kb.isc.org/docs/aa-01123
> 
> —Ben



Dumb question… how do you turn on statistics-channel when building bind?  I’m 
not seeing an option for it in ./configure


-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
Does the named report proper max-cache-size into the log when starting?

Something like:

'max-cache-
size 90%' - setting to 86522MB (out of 96136MB)

Ondrej
--
Ondřej Surý — ISC (He/Him)

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

> On 8. 6. 2025, at 22:45, Philip Prindeville via bind-users 
>  wrote:
> 
> I’m currently doing an “rndc flush” every hour to stop my system from getting 
> exhausted.  I’ll disable that and report back in a few hours.

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
Working on it:


https://github.com/openwrt/packages/pull/26721

Here’s my statistics-channel output:



named-stats.xml
Description: XML document



> On May 18, 2025, at 10:30 PM, Ondřej Surý  wrote:
> 
> Well, you’ve provided basically nothing as leads, so it is hard to tell 
> what’s going on with just output of named -V.
> 
> I would suggest to recompile names with jemalloc enabled and then use 
> jemalloc profiling to see where the memory goes.
> 
> See https://www.isc.org/blogs/2023-BIND-memory-management-explained/ for more 
> details (search for jeprof for tldr).
> 
> Ondrej
> --
> Ondřej Surý — ISC (He/Him)


-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
This is on an embedded system, i.e. a 4-core AMD64 low-power machine with 16GB 
of memory, that uses 2GB of that as a tmpfs.

90% would cripple the system.  I’m going to try 10% (after all, it’s only doing 
name service for 200 machines, maybe 450 RRs, and more than have of the 
machines are IoTs that talk to a small number of external hosts).

It’s computing the max-cache-size that I’ve set:

Jun  8 21:34:08 OpenWrt named[8106]: /etc/bind/named.conf:42: 'max-cache-size 
10%' - setting to 171MB (out of 1714MB)

but no idea where the 1741MB that it is basing that off of is coming from.

Just restarted the service, waited 2 minutes, and redid “rndc stats”:

+++ Statistics Dump +++ (1749440599)
++ Incoming Requests ++
 476 QUERY
  21 UPDATE
++ Incoming Queries ++
 260 A
   2 NS
   3 SOA
   4 PTR
   2 MX
  42 TXT
  66 
  12 SRV
   9 NAPTR
  11 SVCB
  65 HTTPS
++ Outgoing Rcodes ++
 387 NOERROR
  66 NXDOMAIN
  21 NOTAUTH
++ Outgoing Queries ++
[View: default]
 643 A
 449 NS
   1 SOA
   1 PTR
   2 MX
  17 TXT
  91 
   2 SRV
   2 NAPTR
  76 DS
  26 DNSKEY
  74 HTTPS
[View: _bind]
++ Name Server Statistics ++
 497 IPv4 requests received
 134 requests with EDNS(0) received
  21 requests with TSIG received
  21 requests with invalid signature
 474 responses sent
 134 responses with EDNS(0) sent
  21 responses with TSIG sent
 325 queries resulted in successful answer
  18 queries resulted in authoritative answer
 435 queries resulted in non authoritative answer
  62 queries resulted in nxrrset
  66 queries resulted in NXDOMAIN
 315 queries caused recursion
  23 duplicate queries received
  24 Recursive clients high-water
 476 UDP queries received
++ Zone Maintenance Statistics ++
   2 IPv4 notifies sent
++ Resolver Statistics ++
[Common]
[View: default]
1384 IPv4 queries sent
1381 IPv4 responses received
  62 NXDOMAIN received
   3 truncated responses received
 497 query retries
   3 query timeouts
 346 IPv4 NS address fetches
 689 DNSSEC validation attempted
 414 DNSSEC validation succeeded
 275 DNSSEC NX validation succeeded
1274 queries with RTT 10-100ms
 106 queries with RTT 100-500ms
   1 queries with RTT 500-800ms
   4 bucket size
1334 COOKIE send with client cookie only
  50 COOKIE sent with client and server cookie
 160 COOKIE replies received
 150 COOKIE client ok
   3 bad cookie rcode
   2 priming queries
[View: _bind]
   4 bucket size
++ Cache Statistics ++
[View: default]
6324 cache hits
  26 cache misses
 578 cache hits (from query)
 498 cache misses (from query)
   0 cache records deleted due to memory exhaustion
  38 cache records deleted due to TTL expiration
 303 covering nsec returned
1799 cache database nodes
   2 cache NSEC auxiliary database nodes
   0 cache database hash buckets
  988056 cache tree memory in use
   32992 cache heap memory in use
[View: _bind (Cache: _bind)]
   0 cache hits
   0 cache misses
   0 cache hits (from query)
   0 cache misses (from query)
   0 cache records deleted due to memory exhaustion
   0 cache records deleted due to TTL expiration
   0 covering nsec returned
   0 cache database nodes
   0 cache NSEC auxiliary database nodes
   0 cache database hash buckets
   39370 cache tree memory in use
 224 cache heap memory in use
++ Cache DB RRsets ++
[View: default]
1250 A
 326 NS
  95 CNAME
  12 SOA
   1 PTR
   2 MX
  10 TXT
 773 
  38 DS
 111 RRSIG
   2 NSEC
  22 DNSKE

Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
The 1.7GB is what the system is reporting. That’s why I asked as I’ve seen 
OpenWRT reporting weird or no values before.

171MB cache is little on a low side and negative effects from overmem LRU 
cleaning will going to hurt the performance.

I would suggest to set a fixed size for the cache - 1.6GB-2GB should be more 
than enough for your purposes.

Ondrej
--
Ondřej Surý — ISC (He/Him)

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

> On 9. 6. 2025, at 5:45, Philip Prindeville 
>  wrote:
> 
> Jun  8 21:34:08 OpenWrt named[8106]: /etc/bind/named.conf:42: 'max-cache-size 
> 10%' - setting to 171MB (out of 1714MB)
> 
> but no idea where the 1741MB that it is basing that off of is coming from.

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
Jun  8 22:22:10 OpenWrt named[15142]: /etc/bind/named.conf:42: expected integer 
and optional unit or percent near '1638MB'


> On Jun 8, 2025, at 10:17 PM, Ondřej Surý  wrote:
> 
> Yes, there's no math involved, it just honors the limit.
> 
> FTR you can also say:
> 
> max-cache-size 2GB;
> 
> You don't have to specify it to the last byte.
> 
> Ondrej
> --
> Ondřej Surý (He/Him)
> ond...@isc.org
> 
> My working hours and your working hours may be different. Please do not feel 
> obligated to reply outside your normal working hours.
> 
>> On 9. 6. 2025, at 6:12, Philip Prindeville 
>>  wrote:
>> 
>> Odd. I tried:
>> 
>> max-cache-size 1717986918;
>> 
>> and restarted and I don’t see anything in the logs about it.  But I did when 
>> I used a percentage.
>> 
>> 
>> 
>>> On Jun 8, 2025, at 10:02 PM, Ondřej Surý  wrote:
>>> 
>>> The 1.7GB is what the system is reporting. That’s why I asked as I’ve seen 
>>> OpenWRT reporting weird or no values before.
>>> 
>>> 171MB cache is little on a low side and negative effects from overmem LRU 
>>> cleaning will going to hurt the performance.
>>> 
>>> I would suggest to set a fixed size for the cache - 1.6GB-2GB should be 
>>> more than enough for your purposes.
>>> 
>>> Ondrej
>>> --
>>> Ondřej Surý — ISC (He/Him)
>>> 
>>> My working hours and your working hours may be different. Please do not 
>>> feel obligated to reply outside your normal working hours.
>>> 
 On 9. 6. 2025, at 5:45, Philip Prindeville 
  wrote:
 
 Jun  8 21:34:08 OpenWrt named[8106]: /etc/bind/named.conf:42: 
 'max-cache-size 10%' - setting to 171MB (out of 1714MB)
 
 but no idea where the 1741MB that it is basing that off of is coming from.
>>> 
>> 
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
I read:

https://bind9.readthedocs.io/en/v9.20.9/reference.html#namedconf-statement-max-cache-size

and it doesn’t explain the notation for .




> On Jun 8, 2025, at 10:39 PM, Ondřej Surý  wrote:
> 
> What If you actually read the manual that I sent you - syntax of sizeval is 
> explained there.
> --
> Ondřej Surý — ISC (He/Him)
> 
> My working hours and your working hours may be different. Please do not feel 
> obligated to reply outside your normal working hours.
> 
>> On 9. 6. 2025, at 6:34, Philip Prindeville 
>>  wrote:
>> 
>> Maybe GB is the only unit it groks.
>> 
>> 
>> Jun  8 22:31:52 OpenWrt named[19145]: /etc/bind/named.conf:42: expected 
>> integer and optional unit or percent near ‘1536MB’
>> 
>> Nope:
>> 
>> Jun  8 22:32:48 OpenWrt named[19609]: /etc/bind/named.conf:43: expected 
>> integer and optional unit or percent near ‘2GB'
>> 
>> 
>> 
>>> On Jun 8, 2025, at 10:29 PM, Ondřej Surý  wrote:
>>> 
>>> It does have the effect.
>>> 
>>> Also there’s BIND 9 ARM at https://bind9.readthedocs.io/en/v9.20.9/
>>> --
>>> Ondřej Surý — ISC (He/Him)
>>> 
>>> My working hours and your working hours may be differentw . Please do not 
>>> feel obligated to reply outside your normal working hours.
>>> 
> On 9. 6. 2025, at 6:20, Philip Prindeville 
>  wrote:
 
 but doesn’t explain the syntax of “sizeval”.
 
 I tried “1638M” but that doesn’t seem to have an effect.
>> 
>> 
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
Yes, there's no math involved, it just honors the limit.

FTR you can also say:

max-cache-size 2GB;

You don't have to specify it to the last byte.

Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

> On 9. 6. 2025, at 6:12, Philip Prindeville 
>  wrote:
> 
> Odd. I tried:
> 
> max-cache-size 1717986918;
> 
> and restarted and I don’t see anything in the logs about it.  But I did when 
> I used a percentage.
> 
> 
> 
>> On Jun 8, 2025, at 10:02 PM, Ondřej Surý  wrote:
>> 
>> The 1.7GB is what the system is reporting. That’s why I asked as I’ve seen 
>> OpenWRT reporting weird or no values before.
>> 
>> 171MB cache is little on a low side and negative effects from overmem LRU 
>> cleaning will going to hurt the performance.
>> 
>> I would suggest to set a fixed size for the cache - 1.6GB-2GB should be more 
>> than enough for your purposes.
>> 
>> Ondrej
>> --
>> Ondřej Surý — ISC (He/Him)
>> 
>> My working hours and your working hours may be different. Please do not feel 
>> obligated to reply outside your normal working hours.
>> 
>>> On 9. 6. 2025, at 5:45, Philip Prindeville 
>>>  wrote:
>>> 
>>> Jun  8 21:34:08 OpenWrt named[8106]: /etc/bind/named.conf:42: 
>>> 'max-cache-size 10%' - setting to 171MB (out of 1714MB)
>>> 
>>> but no idea where the 1741MB that it is basing that off of is coming from.
>> 
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
It does have the effect.

Also there’s BIND 9 ARM at https://bind9.readthedocs.io/en/v9.20.9/
--
Ondřej Surý — ISC (He/Him)

My working hours and your working hours may be differentw . Please do not feel 
obligated to reply outside your normal working hours.

> On 9. 6. 2025, at 6:20, Philip Prindeville 
>  wrote:
> 
> but doesn’t explain the syntax of “sizeval”.
> 
> I tried “1638M” but that doesn’t seem to have an effect.
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
Odd. I tried:

max-cache-size 1717986918;

and restarted and I don’t see anything in the logs about it.  But I did when I 
used a percentage.



> On Jun 8, 2025, at 10:02 PM, Ondřej Surý  wrote:
> 
> The 1.7GB is what the system is reporting. That’s why I asked as I’ve seen 
> OpenWRT reporting weird or no values before.
> 
> 171MB cache is little on a low side and negative effects from overmem LRU 
> cleaning will going to hurt the performance.
> 
> I would suggest to set a fixed size for the cache - 1.6GB-2GB should be more 
> than enough for your purposes.
> 
> Ondrej
> --
> Ondřej Surý — ISC (He/Him)
> 
> My working hours and your working hours may be different. Please do not feel 
> obligated to reply outside your normal working hours.
> 
>> On 9. 6. 2025, at 5:45, Philip Prindeville 
>>  wrote:
>> 
>> Jun  8 21:34:08 OpenWrt named[8106]: /etc/bind/named.conf:42: 
>> 'max-cache-size 10%' - setting to 171MB (out of 1714MB)
>> 
>> but no idea where the 1741MB that it is basing that off of is coming from.
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
I’ll try to get a smoking gun.

How do you configure an explicit number of bytes with max-cache-size?

The manpage says:

max-cache-size ( default | unlimited |  |  );


but doesn’t explain the syntax of “sizeval”.

I tried “1638M” but that doesn’t seem to have an effect.



> On Jun 8, 2025, at 10:16 PM, Ondřej Surý  wrote:
> 
> I don't see anything wrong with the memory in the attached file - 13MB 
> doesn't seem to be causing any havoc.
> 
> And it roughly matches what I am seeing here with fresh named instance on 
> 64-bit machine:
> 
> $ smem -P name[d]
>  PID User Command Swap  USS  PSS  RSS
> 61387 ondrej   /home/ondrej/Projects/bind90 96841194418628
> 
> Can you send one when you think there's a runaway memory problem? Because 
> this one seems to be sane:
> 
> /statistics/memory/contexts/context/name=OpenSSL
> /statistics/memory/contexts/context/inuse=517912
> /statistics/memory/contexts/context/name=uv
> /statistics/memory/contexts/context/inuse=4864
> /statistics/memory/contexts/context/name=libxml2
> /statistics/memory/contexts/context/inuse=401336
> /statistics/memory/contexts/context/name=named_log
> /statistics/memory/contexts/context/inuse=9512
> /statistics/memory/contexts/context/name=main
> /statistics/memory/contexts/context/inuse=1796991
> /statistics/memory/contexts/context/name=loop-
> /statistics/memory/contexts/context/inuse=2037860
> /statistics/memory/contexts/context/name=loop-0001
> /statistics/memory/contexts/context/inuse=2005796
> /statistics/memory/contexts/context/name=helper-
> /statistics/memory/contexts/context/inuse=0
> /statistics/memory/contexts/context/name=helper-0001
> /statistics/memory/contexts/context/inuse=0
> /statistics/memory/contexts/context/name=zonemgr-mctxpoo
> /statistics/memory/contexts/context/inuse=370549
> /statistics/memory/contexts/context/name=zonemgr-mctxpoo
> /statistics/memory/contexts/context/inuse=341440
> /statistics/memory/contexts/context/name=clientmgr
> /statistics/memory/contexts/context/inuse=836648
> /statistics/memory/contexts/context/name=clientmgr
> /statistics/memory/contexts/context/inuse=962224
> /statistics/memory/contexts/context/name=cache
> /statistics/memory/contexts/context/inuse=1513124
> /statistics/memory/contexts/context/name=cache_heap
> /statistics/memory/contexts/context/inuse=49264
> /statistics/memory/contexts/context/name=ADB
> /statistics/memory/contexts/context/inuse=1848966
> /statistics/memory/contexts/context/name=ADB_dynamic
> /statistics/memory/contexts/context/inuse=147632
> /statistics/memory/contexts/context/name=cache
> /statistics/memory/contexts/context/inuse=38586
> /statistics/memory/contexts/context/name=cache_heap
> /statistics/memory/contexts/context/inuse=112
> /statistics/memory/contexts/context/name=ADB
> /statistics/memory/contexts/context/inuse=664
> /statistics/memory/contexts/context/name=ADB_dynamic
> /statistics/memory/contexts/context/inuse=196784
> /statistics/memory/summary/InUse=13080208
> 
> Ondrej
> --
> Ondřej Surý (He/Him)
> ond...@isc.org
> 
> My working hours and your working hours may be different. Please do not feel 
> obligated to reply outside your normal working hours.
> 
>> Here’s my statistics-channel output:
>> 
>> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
What If you actually read the manual that I sent you - syntax of sizeval is 
explained there.
--
Ondřej Surý — ISC (He/Him)

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

> On 9. 6. 2025, at 6:34, Philip Prindeville 
>  wrote:
> 
> Maybe GB is the only unit it groks.
> 
> 
> Jun  8 22:31:52 OpenWrt named[19145]: /etc/bind/named.conf:42: expected 
> integer and optional unit or percent near ‘1536MB’
> 
> Nope:
> 
> Jun  8 22:32:48 OpenWrt named[19609]: /etc/bind/named.conf:43: expected 
> integer and optional unit or percent near ‘2GB'
> 
> 
> 
>> On Jun 8, 2025, at 10:29 PM, Ondřej Surý  wrote:
>> 
>> It does have the effect.
>> 
>> Also there’s BIND 9 ARM at https://bind9.readthedocs.io/en/v9.20.9/
>> --
>> Ondřej Surý — ISC (He/Him)
>> 
>> My working hours and your working hours may be differentw . Please do not 
>> feel obligated to reply outside your normal working hours.
>> 
 On 9. 6. 2025, at 6:20, Philip Prindeville 
  wrote:
>>> 
>>> but doesn’t explain the syntax of “sizeval”.
>>> 
>>> I tried “1638M” but that doesn’t seem to have an effect.
> 
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Ondřej Surý
I don't see anything wrong with the memory in the attached file - 13MB doesn't 
seem to be causing any havoc.

And it roughly matches what I am seeing here with fresh named instance on 
64-bit machine:

$ smem -P name[d]
  PID User Command Swap  USS  PSS  RSS
61387 ondrej   /home/ondrej/Projects/bind90 96841194418628

Can you send one when you think there's a runaway memory problem? Because this 
one seems to be sane:

/statistics/memory/contexts/context/name=OpenSSL
/statistics/memory/contexts/context/inuse=517912
/statistics/memory/contexts/context/name=uv
/statistics/memory/contexts/context/inuse=4864
/statistics/memory/contexts/context/name=libxml2
/statistics/memory/contexts/context/inuse=401336
/statistics/memory/contexts/context/name=named_log
/statistics/memory/contexts/context/inuse=9512
/statistics/memory/contexts/context/name=main
/statistics/memory/contexts/context/inuse=1796991
/statistics/memory/contexts/context/name=loop-
/statistics/memory/contexts/context/inuse=2037860
/statistics/memory/contexts/context/name=loop-0001
/statistics/memory/contexts/context/inuse=2005796
/statistics/memory/contexts/context/name=helper-
/statistics/memory/contexts/context/inuse=0
/statistics/memory/contexts/context/name=helper-0001
/statistics/memory/contexts/context/inuse=0
/statistics/memory/contexts/context/name=zonemgr-mctxpoo
/statistics/memory/contexts/context/inuse=370549
/statistics/memory/contexts/context/name=zonemgr-mctxpoo
/statistics/memory/contexts/context/inuse=341440
/statistics/memory/contexts/context/name=clientmgr
/statistics/memory/contexts/context/inuse=836648
/statistics/memory/contexts/context/name=clientmgr
/statistics/memory/contexts/context/inuse=962224
/statistics/memory/contexts/context/name=cache
/statistics/memory/contexts/context/inuse=1513124
/statistics/memory/contexts/context/name=cache_heap
/statistics/memory/contexts/context/inuse=49264
/statistics/memory/contexts/context/name=ADB
/statistics/memory/contexts/context/inuse=1848966
/statistics/memory/contexts/context/name=ADB_dynamic
/statistics/memory/contexts/context/inuse=147632
/statistics/memory/contexts/context/name=cache
/statistics/memory/contexts/context/inuse=38586
/statistics/memory/contexts/context/name=cache_heap
/statistics/memory/contexts/context/inuse=112
/statistics/memory/contexts/context/name=ADB
/statistics/memory/contexts/context/inuse=664
/statistics/memory/contexts/context/name=ADB_dynamic
/statistics/memory/contexts/context/inuse=196784
/statistics/memory/summary/InUse=13080208

Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

> Here’s my statistics-channel output:
> 
> 
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Significant memory usage

2025-06-08 Thread Philip Prindeville via bind-users
Maybe GB is the only unit it groks.


Jun  8 22:31:52 OpenWrt named[19145]: /etc/bind/named.conf:42: expected integer 
and optional unit or percent near ‘1536MB’

Nope:

Jun  8 22:32:48 OpenWrt named[19609]: /etc/bind/named.conf:43: expected integer 
and optional unit or percent near ‘2GB'



> On Jun 8, 2025, at 10:29 PM, Ondřej Surý  wrote:
> 
> It does have the effect.
> 
> Also there’s BIND 9 ARM at https://bind9.readthedocs.io/en/v9.20.9/
> --
> Ondřej Surý — ISC (He/Him)
> 
> My working hours and your working hours may be differentw . Please do not 
> feel obligated to reply outside your normal working hours.
> 
>> On 9. 6. 2025, at 6:20, Philip Prindeville 
>>  wrote:
>> 
>> but doesn’t explain the syntax of “sizeval”.
>> 
>> I tried “1638M” but that doesn’t seem to have an effect.


-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users