>
> This is an issue that has plagued Asterisk since day one. Basically there
> is no solution available because there is no way to set aside memory to be
> kept from a growing disk cache. I did some research and this looks like a
> bad design from the Kernel people. Meanwhile all you can do us every 60
> seconds:
echo 3 | sudo tee /proc/sys/vm/drop_caches
Asterisk should be able to reserve memory and force it to stay locked in
memory, exactly like Mariadb does with
memlock=1
Would the Asterisk developers consider something like this?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200926/a3a7fb71/attachment.html>
