From: Dominik Csapak <d.csapak@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Markus Frank <m.frank@proxmox.com>,
pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api] config: adjust max_filters calculation to reflect current memory usage
Date: Wed, 10 Jan 2024 14:40:30 +0100 [thread overview]
Message-ID: <2015aeba-8ed5-4250-901f-6778fdcc27c2@proxmox.com> (raw)
In-Reply-To: <411ba218-cfea-4075-bfb0-bee51cbc6051@proxmox.com>
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@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
>>
>>
>
>
>
> _______________________________________________
> pmg-devel mailing list
> pmg-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
>
>
next prev parent reply other threads:[~2024-01-10 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 11:56 Markus Frank
2024-01-10 12:52 ` Dietmar Maurer
2024-01-10 13:04 ` Markus Frank
2024-01-10 13:38 ` Dominik Csapak
2024-01-10 13:40 ` Dominik Csapak [this message]
2024-01-10 13:57 ` Dietmar Maurer
2024-01-10 14:13 ` Dominik Csapak
2024-01-10 14:32 ` Dietmar Maurer
2024-01-12 10:13 ` Thomas Lamprecht
2024-01-15 18:05 ` Stoiko Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2015aeba-8ed5-4250-901f-6778fdcc27c2@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=m.frank@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox