fix(ci): use 512MB for elasticsearch instead of 32GB

It can be observed that when elasticsearch runs in the CI the process
uses 32GB of resident memory.

Set Xmx and Xms to no more than the threshold that the JVM uses for
compressed object pointers (compressed oops); the exact threshold
varies but is near 32 GB. You can verify that you are under the
threshold by looking for a line in the logs like the following:

Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/docker.html
Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/heap-size.html
This commit is contained in:
Earl Warren 2024-07-16 08:10:58 +02:00
parent 573ba5e9ac
commit d1dadf4e06
WARNING! Although there is a key with this ID in the database it does not verify this commit! This commit is SUSPICIOUS.
GPG key ID: 0579CB2928A78A00

View file

@ -49,6 +49,7 @@ jobs:
image: elasticsearch:7.17.22 image: elasticsearch:7.17.22
env: env:
discovery.type: single-node discovery.type: single-node
ES_JAVA_OPTS: "-Xms512m -Xmx512m"
minio: minio:
image: bitnami/minio:2024.3.30 image: bitnami/minio:2024.3.30
options: >- options: >-