# Elasticsearch and workload

**URL:** <https://discuss.elastic.co/t/elasticsearch-and-workload/184411>\
**Category:** Elasticsearch\
**Created:** [June 5, 2019, 3:29pm UTC](https://discuss.elastic.co/t/elasticsearch-and-workload/184411 "2019-06-05T15:29:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dstromberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dstromberg/32/52956_2.png) [@dstromberg](https://discuss.elastic.co/u/dstromberg)\
**Post date:** [June 5, 2019, 3:29pm UTC](https://discuss.elastic.co/t/elasticsearch-and-workload/184411/1 "2019-06-05T15:29:44Z")

</div>

Hi folks.

We're thinking about having all our logs go to Elasticsearch: One document per log entry.

How should we expect Elasticsearch to perform at about 10\*\*9 small documents of about 150 characters each, across about 30 shards?

Does it matter if we're doing a single, indexed document lookup, or if we're looking at every record in an index?

That is, is Elasticsearch closer to OLTP or Data Warehouse? Or dare I hope: is it good for both?

Also, what is the approximate storage overhead incurred by the indices for that many small documents?

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 3, 2019, 3:30pm UTC](https://discuss.elastic.co/t/elasticsearch-and-workload/184411/2 "2019-07-03T15:30:14Z")

</div>

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