# Machine Configuration for elasticsearch as a database

**URL:** <https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735>\
**Category:** Elasticsearch\
**Created:** [May 22, 2021, 5:35pm UTC](https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735 "2021-05-22T17:35:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anirudhan](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Anirudhan](https://discuss.elastic.co/u/Anirudhan)\
**Post date:** [May 22, 2021, 5:35pm UTC](https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735/1 "2021-05-22T17:35:55Z")

</div>

Hi  
I am trying to move the SQL database into elasticsearch. Successfully flattened the data from SQL into elasticsearch.  
These is the details of the index which was created from SQL to elastic **Doc'sCount : 49201833, Storage Size : 13.7gb.**  
This will be increasing. Our backend is in python. Whenever we try to pull the data through scroll API all my machine RAM is getting used and our flask is getting restarted. Below is the machine which we are using. What should be our ideal machine configuration for that data size?

# H/W path Device Class Description

```
                            system t3a.2xlarge

```

/0 bus Motherboard  
/0/0 memory 64KiB BIOS  
/0/4 processor AMD EPYC 7571  
/0/1 memory 31GiB System memory  
/0/100 bridge 440FX - 82441FX PMC [Natoma]  
/0/100/1 bridge 82371SB PIIX3 ISA [Natoma/Triton II]  
/0/100/1.3 generic 82371AB/EB/MB PIIX4 ACPI  
/0/100/3 display [Amazon.com](http://Amazon.com), Inc.  
/0/100/4 storage [Amazon.com](http://Amazon.com), Inc.  
/0/100/4/0 /dev/nvme0 storage Amazon Elastic Block Store  
/0/100/4/0/1 /dev/nvme0n1 disk 429GB NVMe namespace  
/0/100/4/0/1/1 /dev/nvme0n1p1 volume 399GiB EXT4 volume  
/0/100/5 eth0 network Elastic Network Adapter (ENA)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 26, 2021, 10:59pm UTC](https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735/2 "2021-05-26T22:59:46Z")

</div>

It's not clear what system specs you have in this cluster sorry.

---

<div class="post-metadata">

**Author:** ![Anirudhan](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Anirudhan](https://discuss.elastic.co/u/Anirudhan)\
**Post date:** [May 29, 2021, 11:33am UTC](https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735/3 "2021-05-29T11:33:59Z")

</div>

Hi  
Sorry for the delay in response. System is AWS EC2 instance of type t3a.2xlarge.  
32 GB RAM, 8 core CPU, 400GB SSD harddisk.

---

<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:** [June 26, 2021, 11:34am UTC](https://discuss.elastic.co/t/machine-configuration-for-elasticsearch-as-a-database/273735/4 "2021-06-26T11:34:09Z")

</div>

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