unbound-checkconf memory usage is higher than naively expected

[blackgnezdo]

When processing a file with a lot local-zone/local-data entries unbound-checkconfs RAM footprint grows to 50x the size of the input file.

E.g. the result of running the blacklist generator script is a lot (~100k) of entries like this:

local-zone: "___id___.c.mystat-in.net" redirect
local-data: "___id___.c.mystat-in.net A 0.0.0.0"

unbound-checkconf given this input goes to 510M of maximum resident set size on OpenBSD-6.6-current amd64.

Any chance there's a small tweak that can be applied that will reduce memory usage to something more reasonable?

[blackgnezdo]

unbound-checkconf reports version 1.9.4 at this time.

[ralphdolmans]

This is probably caused by the regional allocation used per local-data. If your goal is to make all these domains unreachable you could try without having local-data for all domains. For example using:

local-zone: "___id___.c.mystat-in.net" refuse

[blackgnezdo]

Thanks @ralphdolmans. I wasn't sure why the original script was using this configuration but the one you proposed is working great and is clearly shorter.