mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-31 14:35:26 +00:00
Code Issues Releases Wiki Activity

Update BIND 9 Memory Explained: link to explanation of the chart

Petr Špaček
2023-09-14 16:10:49 +00:00
parent adebcdeca5
commit 5524d2c865
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
BIND-9-Memory-Explained.md

@@ -167,12 +167,11 @@ jeprof \
/usr/sbin/named **HEAP FILE** --pdf > "jeprof.pdf"
```
See [explanation how to read the chart - same as for Google pprof](https://gperftools.github.io/gperftools/heapprofile.html).
More options can be found in [jeprof](https://manpages.ubuntu.com/manpages/impish/man1/jeprof.1.html) manual page. These must be interpreted with knowledge of the BIND 9 internals. That said, if you are reporting what you think is a memory issue, attaching output of the `jeprof` will certainly help.
### Memory Profiling Example
The output of `jeprof` can look like this (this is how the memory looks like after 1 minute `dnsperf` run).
The output of `jeprof` can look like this (this is how the memory looks like after 1 minute `dnsperf` run):
See [explanation](https://gperftools.github.io/gperftools/heapprofile.html) how to read the chart. It's the same as for Google `pprof` tool, probably because jemalloc's profiling has some common history with `pprof`.
![jeprof](uploads/19504c39a0d7920e57954b1e30dafd27/jeprof.gif)