# Elastic Performance

**URL:** <https://discuss.elastic.co/t/elastic-performance/98884>\
**Category:** Elasticsearch\
**Created:** [August 30, 2017, 3:56pm UTC](https://discuss.elastic.co/t/elastic-performance/98884 "2017-08-30T15:56:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharongur](https://avatars.discourse-cdn.com/v4/letter/s/7993a0/32.png) [@sharongur](https://discuss.elastic.co/u/sharongur)\
**Post date:** [August 30, 2017, 3:56pm UTC](https://discuss.elastic.co/t/elastic-performance/98884/1 "2017-08-30T15:56:12Z")

</div>

Hi all,  
I wonder how\if elastic will handle my requirements:  
20M records a day -\> index 3 years backwards.

My worry is about query performance and not multiple requests. (more shards rather then more nodes)

will elastic handle this amount of data?  
What is the best architecture to handle this load? ( index per day? week? )  
what are the variables my performance will be effected by? my machines memory and size? will infinite memory and size support infinite data per day? (i exaggerate on purpose to learn&understands the relations between machine strength, architecture and performance of elastic)

Thanks in advance!

---

<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:** [September 1, 2017, 2:50am UTC](https://discuss.elastic.co/t/elastic-performance/98884/2 "2017-09-01T02:50:43Z")

</div>

All of this depends on how large each record is.

---

<div class="post-metadata">

**Author:** ![sharongur](https://avatars.discourse-cdn.com/v4/letter/s/7993a0/32.png) [@sharongur](https://discuss.elastic.co/u/sharongur)\
**Post date:** [September 3, 2017, 7:01am UTC](https://discuss.elastic.co/t/elastic-performance/98884/3 "2017-09-03T07:01:26Z")

</div>

It'll be an average document, not 2 large not 2 small. maybe even more leaning towards a small documents, it will have about dozen fields...

---

<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:** [September 3, 2017, 9:05am UTC](https://discuss.elastic.co/t/elastic-performance/98884/4 "2017-09-03T09:05:06Z")

</div>

Average compared to what?

---

<div class="post-metadata">

**Author:** ![sharongur](https://avatars.discourse-cdn.com/v4/letter/s/7993a0/32.png) [@sharongur](https://discuss.elastic.co/u/sharongur)\
**Post date:** [September 3, 2017, 12:30pm UTC](https://discuss.elastic.co/t/elastic-performance/98884/5 "2017-09-03T12:30:31Z")

</div>

It will have 60~ish fields, the fields themselves will not have some base 64's or some very large data. you need the size of every document to give me a an answer?

---

<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:** [September 3, 2017, 8:03pm UTC](https://discuss.elastic.co/t/elastic-performance/98884/6 "2017-09-03T20:03:17Z")

</div>

Saying it's "average" means nothing when the uses for Elasticsearch range from metrics from the Mars rover through to DNA strands or even more "boring" stuff like logs, metrics, emails, PDFs, text.

You're asking a very general question and providing very vague details. Ultimately you will need to test with a set of your data to make sure your structures and queries are optimal for your use case.

---

<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 1, 2017, 8:03pm UTC](https://discuss.elastic.co/t/elastic-performance/98884/7 "2017-10-01T20:03:19Z")

</div>

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