# How can we store large scale data with 32GB RAM / 30TB disk on machine
**URL:** https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501
**Category:** Elasticsearch
**Created:** [May 4, 2017, 8:05am UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501 "2017-05-04T08:05:45Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@hellokitty](https://discuss.elastic.co/u/hellokitty)
#### Post date: [May 4, 2017, 8:05am UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/1 "2017-05-04T08:05:45Z")
My problem is that：
I have some machine which has about 32GB RAM and 30 TB disk storage.
Once the disk usage reach 10%，the memory used may reach up to 90%.
Although I have 30TB but I can not use so much disk storage, because memory is limit.
most percent of RAM cost is FST term index，My ES is 2.3.X.
Please give me some advice!
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [May 4, 2017, 8:16am UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/2 "2017-05-04T08:16:17Z")
Each shard comes with overhead in terms of memory and file handles, so in order to maximise the amount of data a node can hold, make sure your shards are in the tens of GB in size. Having said that, I doubt you will be able to utilise anywhere close to that amount of disk space given the limited amount of RAM you have.
---
### Author:  [@hellokitty](https://discuss.elastic.co/u/hellokitty)
#### Post date: [May 4, 2017, 8:34am UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/3 "2017-05-04T08:34:14Z")
Yeah, I had try some cases to solve my problem, include set each shards to the tens of GB in size. I found that:
in my case, one shard with 70GB in size, the shard may cost about 470 MB term\_memory.
So if I used all of 32GB RAM, means that I can store about 32GB/470MB=68 shards. 68
shards can only store 70GB\*68=4.7TB
😢
---
### Author:  [@rusty](https://discuss.elastic.co/u/rusty)
#### Post date: [May 4, 2017, 3:10pm UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/4 "2017-05-04T15:10:01Z")
You can take a look at [https://github.com/elastic/elasticsearch/issues/24269](https://github.com/elastic/elasticsearch/issues/24269) and vote for it. But IMHO this PR would never accepted by the Elastic team not in 2.x nor in master branch (I'll be happy to be wrong).
---
### Author:  [@hellokitty](https://discuss.elastic.co/u/hellokitty)
#### Post date: [May 8, 2017, 4:51pm UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/5 "2017-05-08T16:51:55Z")
Good, may be we can pull some change to lucene core to unload indices?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 5, 2017, 5:07pm UTC](https://discuss.elastic.co/t/how-can-we-store-large-scale-data-with-32gb-ram-30tb-disk-on-machine/84501/6 "2017-06-05T17:07:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.