Package: unbound Version: 1.4.17-2 Severity: minor Hi,
While setting up unbound to do some testing, I noticed that big local-zones make unbound consume large amounts of memory. About 47KBs per A record. Even though one should probably not be using unbound for this kind of things, it seems a bit disproportionate the amount of memory it requires. Hence the bug report. As a reproducer, add a local-zone in a parsed config file and then run the following script (or something similar) and inject its output into the config file: for a in $(seq 1 254); do for b in $(seq 1 254); do printf " local-data: \"test.local. IN A 127.%d.%d.1\"\n" $a $b done; done (there's nothing special about it, you can also generate the entries in whatever way you want). My estimate, based on a lower number of records, is that for the 64516 generated records, unbound will take around 3032252KBs. Testing was done under x86. x86_64 probably requires more memory. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
