# Large Array Performance Optimization, Resource Costs

**URL:** <https://discuss.elastic.co/t/large-array-performance-optimization-resource-costs/146279>\
**Category:** Elasticsearch\
**Created:** [August 28, 2018, 7:14am UTC](https://discuss.elastic.co/t/large-array-performance-optimization-resource-costs/146279 "2018-08-28T07:14:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [August 28, 2018, 2:14pm UTC](https://discuss.elastic.co/t/large-array-performance-optimization-resource-costs/146279/2 "2018-08-28T14:14:04Z")

</div>

> [@tecfu](#):
>
> the Elasticsearch employee who responded did not provide any meaningful information in their response, they just said be "reasonable".

Your link didn't work for me. The response I saw was this: [What are the limitations of array size in elastic search? - #2 by jpountz](https://discuss.elastic.co/t/what-are-the-limitations-of-array-size-in-elastic-search/108413/2)

If so it seemed a perfectly reasonable answer to me. i.e. don't create a single JSON document with an array of a million ID strings which have to be rewritten entirely each time there's any change to that set.

The workaround would be to break this doc up into smaller ones.

---

_[View the full topic](https://discuss.elastic.co/t/large-array-performance-optimization-resource-costs/146279)._