2.5.0 memory requirements

Technical assistance
1

Infos:

  • Used Zammad version: 2.5.0
  • Used Zammad installation source: zammad-docker-compose
  • Operating system: Amazon Linux (docker updated from 17.12 to 18.03)

Expected behavior:

  • same memory requirements as 2.4

Actual behavior:

  • out of memory after around 6 hours of operation

We had been running the docker containers for some months non-stop on an EC2 t2.medium instance (which has 4GB RAM, the minimum requirement stated at install-docker-compose.html )

This doesn’t seem to be enough for 2.5.0; the machine ran out of memory and had to be forcefully stopped/rebooted.

docker stats show elasticsearch is the bigger consumer of memory:

CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM %
– – – / – –
0320ca62c367 zammaddockercompose_zammad-nginx_1 0.00% 5.48MiB / 7.503GiB 0.07%
0165caeea18a zammaddockercompose_zammad-scheduler_1 0.01% 189.3MiB / 7.503GiB 2.46%
2b58460fa055 zammaddockercompose_zammad-websocket_1 0.04% 138.8MiB / 7.503GiB 1.81%
27b853e0dd4c zammaddockercompose_zammad-backup_1 0.00% 1.664MiB / 7.503GiB 0.02%
67e087474ad7 zammaddockercompose_zammad-railsserver_1 0.00% 190.9MiB / 7.503GiB 2.48%
0df00a6a3af8 zammaddockercompose_zammad-postgresql_1 0.00% 42.02MiB / 7.503GiB 0.55%
c28ad2d57f63 zammaddockercompose_zammad-elasticsearch_1 0.10% 2.253GiB / 7.503GiB 30.03%
e3a1bbcaaa69 zammaddockercompose_zammad-memcached_1 0.03% 19.12MiB / 7.503GiB 0.25%

But it is possible the usage of the others has crept up since 2.4, I don’t have figures for comparison.

2

This might be elasticsearch taking too much memory.
You could take a look at the following link and limit the memory usuage of elasticsearch:

3

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.