[pmg-devel] [PATCH pmg-api] config: adjust max_filters calculation to reflect current memory usage

[Dominik Csapak]

On 1/10/24 14:38, Dominik Csapak wrote:
> On 1/10/24 13:52, Dietmar Maurer wrote:
>>> One pmg-smtp-filter process uses at least 220 MiB.
>>> When having 100000 rules one process can take up to 330 MiB.
>>
>> I guess almost nobody has that many rules! So IMHO, with this patch we
>> are now too conservative for 99% of all installations.
> 
> i think what markus meant is that he had 100000 entries in a who object,
> not rules. That is (sadly) rather realistic and we encounter it often with users/customers.
> (even if we don't recommend it)

after thinking a bit, 100.000 might really be on the large side, but i saw
multiple thousand entries quite often

> 
> i think it's easier than you think to blow up the filter memory usage, we're already
> 100 MiB up from the initial assumption without adding any new rules/objects by default.
> (e.g. a new spamassassin update can increase that probably quite easily)
> 
> while 300 might be excessive, on our machines we easily observe 230 MiB per worker
> so that could be a fine value (like Markus suggested)
> 
>>
>> Besides, the rule system is not meant to be used as large block-list. People should set-up a RBL 
>> server instead, which is far more effective.
>>
>> - Dietmar
>>
>>
>> _______________________________________________
>> pmg-devel mailing list
>> pmg-devel at lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
>>
>>
> 
> 
> 
> _______________________________________________
> pmg-devel mailing list
> pmg-devel at lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
> 
>