[solved] Zammad memory leak?

[SEGGER-NV]

Hi,

Agreed that it is not a solution but a mere workaround.
Our PGSQL config has only changed in default in max_connections from default 100 to 200 as we got internal 500 errors when increasing web_concurrecny.
See here for more info: [SOLVED] Internal server error 500 when WEB_CONCURRENCY is set >1 - #5 by SEGGER-NV

However these two changes started the slow but constant increase of memory usage.

@MrGeneration

Problem is, dozens of people use Zammad in productive with even more concurrent active agents.

Do they have regular maintenance periods where servers or services might be restarted?
Or do they have 0 maintenance 100% uptime setups?

@MrGeneration

Small hint regarding killing of processes: This is a linux behavior you can configure.
And another thing: You should always try to avoid to use swap, as your systems performance will decrease significantly.

Fair enough, but it should have never gotten to that point. The swappiness of the system is currently set to start using swap if less than 10% memory are available.

Br,
Nino