By default, when you start Elasticsearch, the heap size of the JVM is 2GB. The more memory available to Elasticsearch, the more memory it can use for caching, which improves the overall performance. Also, to run aggregations on your data, there are memory considerations. When you are ready for production, it important to make sure Elasticsearch has enough memory. You can monitor the heap usage and garbage collections using the node stats API. You can configure the JVM settings, such as heap size, garbage collection, and so on in the jvm.options file in the config directory.
Let's look at the elasticsearch1 memory usage using the node stats API as shown next:
http://127.0.0.1:9200/_nodes/elasticsearch1/stats/jvm?human ...
