# Elastic Search Node Configs **URL:** \ **Category:** Elasticsearch\ **Created:** [July 7, 2019, 3:01pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252 "2019-07-07T15:01:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![adwaitjoshi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adwaitjoshi/32/35098_2.png) [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)\ **Post date:** [July 7, 2019, 3:01pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/1 "2019-07-07T15:01:32Z")
I have seen people using multiple nodes on the same physical/virtual machine, I wanted to ask if there is an advantage to this. Logically, the disk space will be used for 2 copies also if the disk (or the RAID array dies) your data is toast, and your storage will be halved, but is there a significant advantage to having this config? Do the read/writes perform significantly better? I have a cluster environment on 2 physical machines that I an trying to setup, what I am essentially looking for is fast writes and fast reads through Kibana searches and dashboards. Whats the optimal config on this? I have 2 machines of 8C/64GB/4.8TB SSD machine which is dedicated to ELK. We also have about 3 billion total transactions that around 30 to 50 users can be querying. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 7, 2019, 4:27pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/2 "2019-07-07T16:27:02Z")
People sometimes run multiple nodes on a single machine if it has a lot of RAM (remembering that Elasticsearch should have a [maximum heap size of no more than ~31GB, ideally less](https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html)) or if they want to attach SSDs and spinning disks to the same machine and control which shards are allocated to each storage class. It involves more admin, and a little more performance overhead than a single node, so it's best to avoid this unless your benchmarks show it to be worth it. ---
**Author:** ![adwaitjoshi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adwaitjoshi/32/35098_2.png) [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)\ **Post date:** [July 7, 2019, 7:57pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/3 "2019-07-07T19:57:05Z")
Right....so if I want fast searches and disk writes along with fast load times on dashboards, what is the ideal config. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 7, 2019, 8:13pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/4 "2019-07-07T20:13:38Z")
I'd guess one node per machine, but it very much depends on your use case. The only way to be sure is to measure it. ---
**Author:** ![adwaitjoshi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adwaitjoshi/32/35098_2.png) [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)\ **Post date:** [July 7, 2019, 9:09pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/5 "2019-07-07T21:09:25Z")
What method would you recommend for measuring? Anything specific or just standard linux commands/metric beat system plugin? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 7, 2019, 10:20pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/6 "2019-07-07T22:20:36Z")
[Rally](https://esrally.readthedocs.io/en/stable/) is the standard tool for benchmarking Elasticsearch clusters. I'm not an expert on its use, however, so if you have more detailed questions then I recommend opening another thread. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 4, 2019, 10:20pm UTC](https://discuss.elastic.co/t/elastic-search-node-configs/189252/7 "2019-08-04T22:20:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.