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

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 18/01/2024 um 15:55 schrieb Markus Frank:
> Change max_filters calculation for systems with recommended memory
> setup (>4GB).
> 
> The values of 2816 and 150 are based on testing with 4GB, 6GB & 8GB
> memory configurations, large and small numbers of added objects and
> sending multiple mails simultaneously.
> 
> On setups with less memory, it is difficult to completely prevent OOM kills.
> So for these setups the calculation remains similar, but a warning is sent.
> 
> Related OOM killer problem found in forum:
> https://forum.proxmox.com/threads/123531/
> 
> Signed-off-by: Markus Frank <m.frank@proxmox.com>
> ---
> Tested edge cases with setting min_servers to max_servers
> in src/bin/pmg-smtp-filter
> 
>  src/PMG/Config.pm | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
>

applied, , thanks!

but I reworked the heuristic again a bit to avoid the downward glitch when
crossing the 3840 MiB boundary, old/new comparison of max_servers (the actual
count, i.e. get_max_filters() + 2):

 GiB     # max old        # max new
 0.5       5               5
 1.0       9               7
 1.5       13              8
 2.0       13              10
 2.5       17              11
 3.0       22              12
 3.5       26              13
 4.0       13              15
 4.5       16              18
 5.0       20              22
 5.5       23              25
 6.0       27              28
 6.5       30              32
 7.0       34              35
 7.5       37              39
 8.0       40              40

This should be a bit less confusing than the old one.