Elastic Cloud Memory Split

The Elasticsearch guide recommends giving half of the available memory to system cache for lucene-based caching. In the elasticcloud offering, all of the options seem to give everything but 1.5gb of the total memory to elasticsearch. This will no doubt improve heap based operations, but is there a way where we can configure the memory dedicated to es and to os.

How have you reached that conclusion? As far as I know Elastic Cloud follows best practices and gives 50% of RAM to heap for data nodes. This is not configurable.


The options here (IO/Compute/Memory optimized) all show about 1.5 gigs more than ES memory.

I do not know about that so need to leave that to someone from the Cloud team.

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