# Field data for analyzed fields - how can I find out how much heap is required?

**URL:** <https://discuss.elastic.co/t/field-data-for-analyzed-fields-how-can-i-find-out-how-much-heap-is-required/45075>\
**Category:** Elasticsearch\
**Created:** [March 22, 2016, 8:06am UTC](https://discuss.elastic.co/t/field-data-for-analyzed-fields-how-can-i-find-out-how-much-heap-is-required/45075 "2016-03-22T08:06:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lextoumbourou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lextoumbourou/32/8592_2.png) [@lextoumbourou](https://discuss.elastic.co/u/lextoumbourou)\
**Post date:** [March 22, 2016, 8:06am UTC](https://discuss.elastic.co/t/field-data-for-analyzed-fields-how-can-i-find-out-how-much-heap-is-required/45075/1 "2016-03-22T08:06:31Z")

</div>

Hi guys,

I'm trying to perform a Terms Aggregation on an analyzed field (top words used by authors) and I'm hitting CircuitBreakerExceptions. I understand why, and I understand that I can't use doc values here. So the next step is to increase the heap size (and probably get some more memory). So my questions are:

1. I understand that I can learn about how much memory my field data is consuming using the Node Stats API. However, since my query CircuitBreaker-ed, I'm guessing the entire data set wasn't loaded into field data memory. So, is there a way to figure out how much memory in total would be required by a field to be stored in memory so I can plan hardware requirements?

2. Any other suggestions for how we could perform something similar to a Terms Aggregation on a large analyzed field?

Thanks guys!

---

<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:06pm UTC](https://discuss.elastic.co/t/field-data-for-analyzed-fields-how-can-i-find-out-how-much-heap-is-required/45075/2 "2017-07-05T23:06:23Z")

</div>


