# Elastic Cluster Good Configuration for better performance

**URL:** <https://discuss.elastic.co/t/elastic-cluster-good-configuration-for-better-performance/248144>\
**Category:** Elasticsearch\
**Created:** [September 10, 2020, 10:11am UTC](https://discuss.elastic.co/t/elastic-cluster-good-configuration-for-better-performance/248144 "2020-09-10T10:11:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Naveena1](https://avatars.discourse-cdn.com/v4/letter/n/a4c791/32.png) [@Naveena1](https://discuss.elastic.co/u/Naveena1)\
**Post date:** [September 10, 2020, 10:11am UTC](https://discuss.elastic.co/t/elastic-cluster-good-configuration-for-better-performance/248144/1 "2020-09-10T10:11:42Z")

</div>

Hi Team,

Please help me with good configuration for the cluster to improve the performance.

My requirement was :-  
we are using Cluster 7.9.1

```auto
  We have an employee table which has around 30 columns and total records in this table are around 30million records.
select * from employee where id= '12345';

QueryBuilders.matchQuery("id", "12345");
or 
QueryBuilders.termQuery("id.keyword", "12345");

```

I have used matchquery /termquery to replace above query in my API..but using both didnt have much difference.

If the above implementation is good , should we check on the configuration side to increase performance

```auto
To hold some n million/billion of records. ( Around 50-60GB) what should be the 
1. configuration of cluster, 
2. number of nodes, 
3. what is the heap memory, 
4. CPU Cores ?
5. Number of shard in index ?
6. Do we need to use replicas in index ? 

```

Thanks,  
Naveena.

Thanks,`Preformatted text``Preformatted text`

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 10, 2020, 10:46am UTC](https://discuss.elastic.co/t/elastic-cluster-good-configuration-for-better-performance/248144/2 "2020-09-10T10:46:12Z")

</div>

Your query is good. I'd prefer using a term query.

May I suggest you look at the following resources about sizing:

> **[Quantitative Cluster Sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)**

> **[How many shards should I have in my Elasticsearch cluster?](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**

> **[Managing your black Friday logs - CloudConf.IT](https://www.slideshare.net/dadoonet/managing-your-black-friday-logs-cloudconfit-93309899)**
>
> Monitoring an entire application is not a simple task, but with the right tools it is not a hard task either. However, events like Black Friday can push your a…

[![](https://us1.discourse-cdn.com/elastic/original/3X/7/c/7c2edebd5bac194c58a5df87ede6872cb41d61a8.jpeg "Managing your Black Friday Logs, Pablo Musa, Elastic, TechSummit Amsterdam") ](https://www.youtube.com/watch?v=ilP7tG6tabI)

And [Using Rally to Get Your Elasticsearch Cluster Size Right | Elastic Videos](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 8, 2020, 10:46am UTC](https://discuss.elastic.co/t/elastic-cluster-good-configuration-for-better-performance/248144/3 "2020-10-08T10:46:12Z")

</div>

Closed on October 8, 2020, 10:46am UTC

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