all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-docs] bump minimum memory requirement
Date: Wed, 26 Feb 2025 16:29:45 +0100	[thread overview]
Message-ID: <20250226162945.483b740e@rosa.proxmox.com> (raw)
In-Reply-To: <6558281e-e0fd-4694-b196-6381b1b20acb@proxmox.com>

On Wed, 26 Feb 2025 15:53:49 +0100
Thomas Lamprecht <t.lamprecht@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@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).




_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel


  reply	other threads:[~2025-02-26 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 14:07 Dominik Csapak
2025-02-26 14:19 ` Stoiko Ivanov
2025-02-26 14:24 ` Thomas Lamprecht
2025-02-26 14:36   ` Stoiko Ivanov
2025-02-26 14:53     ` Thomas Lamprecht
2025-02-26 15:29       ` Stoiko Ivanov [this message]
2025-02-26 15:38         ` Thomas Lamprecht
2025-02-26 14:45   ` Gabriel Goller

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=20250226162945.483b740e@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    --cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal