# Elastic performance with growth rate of about 150gb in a week

**URL:** <https://discuss.elastic.co/t/elastic-performance-with-growth-rate-of-about-150gb-in-a-week/46634>\
**Category:** Elasticsearch\
**Created:** [April 7, 2016, 7:38am UTC](https://discuss.elastic.co/t/elastic-performance-with-growth-rate-of-about-150gb-in-a-week/46634 "2016-04-07T07:38:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roni](https://avatars.discourse-cdn.com/v4/letter/r/eada6e/32.png) [@Roni](https://discuss.elastic.co/u/Roni)\
**Post date:** [April 7, 2016, 7:38am UTC](https://discuss.elastic.co/t/elastic-performance-with-growth-rate-of-about-150gb-in-a-week/46634/1 "2016-04-07T07:38:55Z")

</div>

Hi, we have an ongoing project based on elastic for two years almost. We have a search engine that works as "google" on documents indexed in elastic. Today we have about 300,000,000 documents with a total size of 2.3tb. We want to take this project to the next level and index about 10 times the amount we have at this moment. It's important to mention that we are not deleting anything, and the growth rate is about 200gb of documents data in a week. We are not limited by nodes hardware, but I'm afraid that good hardware is just not enough in this case. We thought about using the integration you have with Hadoop but we are not too familiar with Hadoop yet. What do you think? 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:01pm UTC](https://discuss.elastic.co/t/elastic-performance-with-growth-rate-of-about-150gb-in-a-week/46634/2 "2017-07-05T23:01:35Z")

</div>

Closed on July 5, 2017, 11:01pm UTC


