Hello Aleš,
I have verified that one instance of the RRL module takes 12.5 MiB, as it contains a big
hash table.
So it's reasonable to configure it as a global-module in the default template. Also I
have found
insufficiently optimized memory allocation in the statistics module for disabled metrics.
This will be
improved in the next release.
Daniel
On 03/16/2018 04:12 PM, Daniel Salzman wrote:
Hi Aleš,
Interesting :-) I will look at it!
I think you could configure the modules (at least rrl) common for all zones, see
https://www.knot-dns.cz/docs/2.6/singlehtml/index.html#global-module
Best,
Daniel
On 03/16/2018 04:03 PM, Aleš Rygl wrote:
> Hello Daniel
>
> to my big surprise, when mod-rrl is disabled, memory consumption is nearly
negligible!
>
> root@eira:~# uptime
> 15:59:34 up 0 min, 1 user, load average: 0.15, 0.03, 0.01
> root@eira:~#
> root@eira:~# free -h
> total used free shared buff/cache available
> Mem: 2.0G 54M 1.8G 2.9M 78M 1.8G
> Swap: 0B 0B 0B
> root@eira:~#
> root@eira:~# systemctl start knot
> root@eira:~#
> root@eira:~# free -h
> total used free shared buff/cache available
> Mem: 2.0G 56M 1.8G 2.9M 81M 1.8G
> Swap: 0B 0B 0B
> root@eira:~#
>
>
> From proces status:
>
> VmPeak: 22952964 kB
> VmSize: 22952964 kB
> VmLck: 0 kB
> VmPin: 0 kB
> VmHWM: 9128 kB
> VmRSS: 8984 kB
> RssAnon: 2820 kB
> RssFile: 6164 kB
> RssShmem: 0 kB
> VmData: 47496 kB
> VmStk: 132 kB
> VmExe: 516 kB
> VmLib: 11488 kB
> VmPTE: 320 kB
> VmPMD: 24 kB
> VmSwap: 0 kB
>
> What do you think about it?
>
> BR
>
> Ales
>
>
>
> On 16.3.2018 15:47, Aleš Rygl wrote:
>> Hello Daniel.
>>
>>
>> On 16.3.2018 10:55, Daniel Salzman wrote:
>>> Aleš,
>>>
>>> On 03/16/2018 10:32 AM, Aleš Rygl wrote:
>>>> Hi Daniel, hi all.
>>>>
>>>> I completely agree that VmSize is not the right metric and I was not
mentioning it in my original post :-) I'd rather point out that Knot is in my case
consuming nearly 2Gig of RAM while serving just 141 zones with 1MB of records while Bind
serving 1560 zones (10% on DNSSEC) something about 550MB =-O
>>>>
>>>> root@eira:~# free -h
>>>> total used free shared buff/cache
available
>>>> Mem: 2.0G 1.7G 122M 5.4M 126M 109M
>>>> Swap: 0B 0B 0B
>>>> root@eira:~#
>>>> root@eira:~# systemctl stop knot.service
>>>> root@eira:~#
>>>> root@eira:~# free -h
>>>> total used free shared buff/cache
available
>>>> Mem: 2.0G 54M 1.8G 5.4M 126M 1.8G
>>>> Swap: 0B 0B 0B
>>>> root@eira:~#
>>>>
>>>> Is it something what I have to count on when using Knot? I am just
surprised by such memory requirements and your measurement shows that it is like that. I
will have to add some RAM...
>>> Probably I don't understand. Knot consumed less physical memory than Bind
during my test :-)
>>>
>>> To be honest, I don't understand why Knot is consuming such amount of
memory in your case!
>>> Could you please try disabling the statistics module? Statistics per zone
with all metrics consume
>>> some memory.
>>>
>> Of course, you are right, I have somehow overlooked it. Sorry for confusion.
>>
>> I have tried to disable all statistics in the config. It is much better now.
Freshly rebooted server and knot started.
>>
>> root@eira:~# systemctl start knot.service
>> root@eira:~# free -h
>> total used free shared buff/cache available
>> Mem: 2.0G 758M 1.1G 2.9M 80M 1.1G
>> Swap: 0B 0B 0B
>> root@eira:~#
>>
>> From process status in /proc:
>>
>> VmPeak: 24751880 kB
>> VmSize: 24686344 kB
>> VmLck: 0 kB
>> VmPin: 0 kB
>> VmHWM: 1742692 kB
>> VmRSS: 1742584 kB
>> RssAnon: 1736288 kB
>> RssFile: 6296 kB
>> RssShmem: 0 kB
>> VmData: 1780864 kB
>> VmStk: 132 kB
>> VmExe: 516 kB
>> VmLib: 11488 kB
>> VmPTE: 3704 kB
>> VmPMD: 32 kB
>> VmSwap: 0 kB
>>
>> BR
>> Ales