Have a look at the mem persentages. It’s not a ruby process but a Java process taking 50% of your memory. If I’d had to guess it’s javascript.
Look up their documentation for “heap size”. You can limit the memory consumption of Elasticsearch. 2-4 GB memory should be good enough.
Also, press “c” in your top to actually see which process exactly is running that will help you in future situations. Or use htop for easier sorting CPU vs Memory etc etc.
Would you advise how can we limit the memory consumption of Elasticsearch in Zammad server side? I’ve increased the RAM to 32GB and I guess if we limit Elasticsearch to maybe 4GB then the rest will be used as caching purpose, this is even better for speeding up the searching by the end users and agent, is my understanding correct?