We got this message
“We would need Elasticsearch to be installed on the server since the old search engines are obsolete.
Minimum requirements for Elasticsearch are 16 CPU cores, 32GB RAM, and 500GB SSD.
You’d need a dedicated server to run it properly.”
Just wondering what the rest of you are doing, did you go ahead and set up Elasticsearch, or are you using something else that works fine?
Would love to hear how you’ve handled this.
Hey @Maggie1
We’ve seen the same situation with Elasticsearch — it’s definitely the way forward. Depending on your data size, a managed service or slightly smaller setup can still work really well.
If you don’t mind, share your contact info — our technical team can help you better and guide you through some options.
Hello Maggie,
yes, that could be true - depending on your data.
4 cores + 8GB for the minimum requirement.
8 cores + 16GB suggested. - it is the standard hardware recommendation for ElasticSearch and OpenSearch (there has been a fork and open source license back and forth).
Since moving to Elasticsearch is technically quite a step and on another level than simply setting up a LAMP server for a CRM, most of my customers try to push it into the future - what usually works quite well, depending on the requirements.
Why do you need ES? You’ve got multiple millions of records to search through?
Question: when we should use ES? Is it always good option to enable for better search results across CRM?
It usually depends on the project.
But some indicators / requirements could be:
Usually in combination: If multiple millions + fuzzy search, then I’d suggest ElasticSearch.
But some customers have smaller databases and insist on fuzzy + full text (+ speed).
Hi @Maggie1,
Those published elastic specs (16 cores / 32GB RAM / 500GB NVME) are production cluster scale for very high ingest + multiple million documents per index.
Most SuiteCRM installs do not need that.
What most real SuiteCRM implementers do today:
Elasticsearch single node, trimmed:
Run with 4-8 cores + 8-16GB RAM, SSD ~50-200GB. Very stable and perfectly fine for SuiteCRM datasets < 10M records
OpenSearch single node (SuiteCRM 8+)
drop-in Elasticsearch compatible + more relaxed licensing + resource reqs similar to trimmed ES