# Eager global ordinals & doc values memory consumption

**URL:** <https://discuss.elastic.co/t/eager-global-ordinals-doc-values-memory-consumption/24725>\
**Category:** Elasticsearch\
**Created:** [July 1, 2015, 1:41pm UTC](https://discuss.elastic.co/t/eager-global-ordinals-doc-values-memory-consumption/24725 "2015-07-01T13:41:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![orenor](https://avatars.discourse-cdn.com/v4/letter/o/e95f7d/32.png) [@orenor](https://discuss.elastic.co/u/orenor)\
**Post date:** [July 1, 2015, 1:41pm UTC](https://discuss.elastic.co/t/eager-global-ordinals-doc-values-memory-consumption/24725/1 "2015-07-01T13:41:12Z")

</div>

Hello,  
just started using the [Eager global ordinals](https://www.elastic.co/guide/en/elasticsearch/guide/current/preload-fielddata.html#eager-global-ordinals) option on my mapping along with doc\_values (for reducing memory consumption) . Though still not loading any field data as expected, I notice a major increase in segment.memory\_in\_bytes. Does ordinals setting keep segments in memory for faster ordinal/segments updates or something?

Any help on this would be appreciated.

Oren

segments: {  
count: 1577  
memory\_in\_bytes: 12222041370  
index\_writer\_memory\_in\_bytes: 12371428  
index\_writer\_max\_memory\_in\_bytes: 5404296015  
version\_map\_memory\_in\_bytes: 9874984  
fixed\_bit\_set\_memory\_in\_bytes: 0  
}

---

<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, 12:04am UTC](https://discuss.elastic.co/t/eager-global-ordinals-doc-values-memory-consumption/24725/2 "2017-07-06T00:04:13Z")

</div>