# Question on index field cache stats reported per node

**URL:** https://discuss.elastic.co/t/question-on-index-field-cache-stats-reported-per-node/9136
**Category:** Elasticsearch
**Created:** [September 25, 2012, 1:17pm UTC](https://discuss.elastic.co/t/question-on-index-field-cache-stats-reported-per-node/9136 "2012-09-25T13:17:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Jan\_Fiedler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jan_fiedler/32/2518_2.png) [@Jan\_Fiedler](https://discuss.elastic.co/u/Jan_Fiedler)
#### Post date: [September 25, 2012, 1:17pm UTC](https://discuss.elastic.co/t/question-on-index-field-cache-stats-reported-per-node/9136/1 "2012-09-25T13:17:35Z")

</div>

I am doing some testing on memory consumption for term facets. I ran a test  
where I index some content and calculate a terms facet on it. I am using  
the node stats request to learn about the field cache size (after  
calculating the facet). My expectation was that I see different memory  
consumption when I go from string to integer or even byte fields. The  
strange thing is that the field cache size reported by the node stats is  
always the same (regardless of the field value type being faceted). Does  
the stats (maybe) only measure the field cache array size (without the  
actual field values)?

--

---

<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 6, 2017, 3:11am UTC](https://discuss.elastic.co/t/question-on-index-field-cache-stats-reported-per-node/9136/2 "2017-07-06T03:11:29Z")

</div>


