[pmg-devel] [PATCH pmg-docs] bump minimum memory requirement

[Thomas Lamprecht]

Am 26.02.25 um 16:29 schrieb Stoiko Ivanov:
> On Wed, 26 Feb 2025 15:53:49 +0100
> Thomas Lamprecht <t.lamprecht at proxmox.com> wrote:
> 
>> Am 26.02.25 um 15:36 schrieb Stoiko Ivanov:
>>> On Wed, 26 Feb 2025 15:24:51 +0100
>>> Thomas Lamprecht <t.lamprecht at proxmox.com> wrote:
>>>   
>>>> Am 26.02.25 um 15:07 schrieb Dominik Csapak:  
>>>>> since a while, we need more than 4 GiB memory for pmg, because
>>>>> clamd/clamav requires more than before.    
>>>>
>>>> But only for ZFS where by default ARC takes up half of memory?  
>>> 2G Ram only does not work too well with clamav (maybe after/when
>>> updating only) - at least on my test-containers, where ARC should not be
>>> counted towards their cgroup memory limit I've seen a few OOM-kills of
>>> clamav when setting 2G IIRC.  
>>
>>
>> Looking at an installed system here and following your and Gabriel's
>> reply it would look like we should increase the minimum requirement to
>> 2.5 GiB and keep 4 GiB for recommended minimum ones.
>>
>> As the minimum requirement basically should cover the needs to get
>> it installed and up and running. I did some heavy testing with millions
>> of mails per day on PMG installations with 4 GiB of memory, worked out
>> fine. One of our production PMGs also has just 4 GiB total memory, while
>> the other has 8 GiB but hovers around 3.8 - 3.9 GiB usage, so I really
>> do not see why we should increase the recommended memory to 6 GiB...
> 
> 2.5 GiB as minimum should work as well (after checking a few systems with
> ClamAV running) - and I see the point of minimum meaning minimum
> 
> as for the recommended - that depends a bit if you have other signatures
> enabled (securite raises this a bit), or another antivirus running - and
> if we want to cover that in the recommended setting - then I'd say 5G (if
> only to not have to change that again when clamAV signatures grow some
> more).

No, I do not want to cover opt-in additional stuff, as where does one
cuts the line there? And third-party tools can require dozens of GiB if
they are some crazy "AI" tool or what not, so not sure how we could say
5 GiB will cover Extra Stuff™.

A generic hint that using opt-in features, extra signatures or third party
tools requiring more memory might still be good though to clarify that we
indeed can only (sanely) state the recommendations for a base system.