mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-09-03 16:15:27 +00:00
Code Issues Releases Wiki Activity

Update BIND 9 Memory Explained

Ondřej Surý
2022-12-08 14:59:34 +00:00
parent e796320c82
commit 78a57e98d1
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
BIND-9-Memory-Explained.md

@@ -111,11 +111,9 @@ jeprof \
More options can be found in [jeprof](https://manpages.ubuntu.com/manpages/impish/man1/jeprof.1.html) manual page, and can't be taken as is, but must be interpreted with knowledge of BIND 9 internals. That said if you are reporting what you think is a memory issue, attaching output of the `jeprof` will certainly help. More options can be found in [jeprof](https://manpages.ubuntu.com/manpages/impish/man1/jeprof.1.html) manual page, and can't be taken as is, but must be interpreted with knowledge of BIND 9 internals. That said if you are reporting what you think is a memory issue, attaching output of the `jeprof` will certainly help.
The output can look like this (this is how the memory looks like after inserting 100k zones via catalog zones and then deleting them): ## Graphs
![jeprof](uploads/0d3e052e5a25e19bf44de2aa956d9066/jeprof.gif) ### Resolver Benchmarks
## Some measurements
To support what has been said in this article, here are some basic graphs comparing 9.11, 9.16, 9.18, and 9.19 (codenamed as `main`). To support what has been said in this article, here are some basic graphs comparing 9.11, 9.16, 9.18, and 9.19 (codenamed as `main`).
@@ -124,3 +122,9 @@ As you can see, the 9.18 and 9.19 memory usage is in the same ballpark as 9.11,
![all-latency-since_0-until_60-2](uploads/bcbd74704b6cce50fcdf29ac131d50d0/all-latency-since_0-until_60-2.png) ![all-latency-since_0-until_60-2](uploads/bcbd74704b6cce50fcdf29ac131d50d0/all-latency-since_0-until_60-2.png)
![all-latency-since_60-until_120](uploads/7767f7276982a4eda11806cb5130c69f/all-latency-since_60-until_120.png) ![all-latency-since_60-until_120](uploads/7767f7276982a4eda11806cb5130c69f/all-latency-since_60-until_120.png)
![all-resmon.memory.current-docker](uploads/0130242517994173bf12df6c7d9785f6/all-resmon.memory.current-docker.png) ![all-resmon.memory.current-docker](uploads/0130242517994173bf12df6c7d9785f6/all-resmon.memory.current-docker.png)
### Catalog Zones Memory Profiling
The output of `jeprof` can look like this (this is how the memory looks like after inserting 100k zones via catalog zones and then deleting them):
![jeprof](uploads/0d3e052e5a25e19bf44de2aa956d9066/jeprof.gif)