# Global ordinals performance and size on-heap

**URL:** https://discuss.elastic.co/t/global-ordinals-performance-and-size-on-heap/158320
**Category:** Elasticsearch
**Created:** [November 27, 2018, 10:48am UTC](https://discuss.elastic.co/t/global-ordinals-performance-and-size-on-heap/158320 "2018-11-27T10:48:40Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)
#### Post date: [November 29, 2018, 6:51am UTC](https://discuss.elastic.co/t/global-ordinals-performance-and-size-on-heap/158320/7 "2018-11-29T06:51:21Z")

</div>

I agree. What we saw is exponential growth in the time it takes to load global ordinals for high cardinality fields, so 30M docs with a field with 30M unique values might take 30s but 70M will take much longer.

The query was a simple terms aggregation on the high cardinality field, with match\_all or any other type of query. We can send hot\_threads next week.

We can share our full sample data we use for testing (on S3), we can send details privately.

---

_[View the full topic](https://discuss.elastic.co/t/global-ordinals-performance-and-size-on-heap/158320)._