# Can I use ES for 100 GB of Data?

**URL:** <https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510>\
**Category:** Elasticsearch\
**Created:** [August 17, 2015, 2:27pm UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510 "2015-08-17T14:27:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![N\_M\_10](https://avatars.discourse-cdn.com/v4/letter/n/f19dbf/32.png) [@N\_M\_10](https://discuss.elastic.co/u/N_M_10)\
**Post date:** [August 17, 2015, 2:27pm UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/1 "2015-08-17T14:27:31Z")

</div>

We have around 100 GB of data, so can i use Elasticsearch for searching in this huge amount of data, will it give response in ms ? If yes than what should be the machine configuration to make it respond within 200ms?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 17, 2015, 2:36pm UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/2 "2015-08-17T14:36:00Z")

</div>

100 GB isn't a lot of data. The machine configuration you need for reasonable query performance depends on various factors, including how the data is mapped, what kind of queries you make, and how many concurrent queries you expect. To give you _some_ kind of idea, I have ~300 GB data on each 64 GB RAM VM node with four cores. The Kibana query performance is adequate but on the slow side.

---

<div class="post-metadata">

**Author:** ![N\_M\_10](https://avatars.discourse-cdn.com/v4/letter/n/f19dbf/32.png) [@N\_M\_10](https://discuss.elastic.co/u/N_M_10)\
**Post date:** [August 18, 2015, 6:50am UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/3 "2015-08-18T06:50:32Z")

</div>

Sorry, first of all our data is 300 GB, and as far as query is concerned we are not using aggregation or the prefix queries, but ngram tokenizers are used, and we have 5 node cluster 2 client node (load balancer) and 3 master+data node.  
As far as machines are concern they have 4 cores & 4 GB of RAM each, will it suffice or we need to upgrade?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 18, 2015, 6:58am UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/4 "2015-08-18T06:58:33Z")

</div>

That's very hard to say, but my hunch is that it'll be enough. If you have any amount of non-analyzed fields you can decrease the RAM need by enabling doc values.

---

<div class="post-metadata">

**Author:** ![N\_M\_10](https://avatars.discourse-cdn.com/v4/letter/n/f19dbf/32.png) [@N\_M\_10](https://discuss.elastic.co/u/N_M_10)\
**Post date:** [August 18, 2015, 6:59am UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/5 "2015-08-18T06:59:44Z")

</div>

cool then  
thanks

---

<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:** [July 5, 2017, 11:55pm UTC](https://discuss.elastic.co/t/can-i-use-es-for-100-gb-of-data/27510/6 "2017-07-05T23:55:24Z")

</div>


