# Very slow search performance after upgrade to 7.16.1

**URL:** <https://discuss.elastic.co/t/very-slow-search-performance-after-upgrade-to-7-16-1/296152>\
**Category:** Elasticsearch\
**Created:** [February 3, 2022, 7:02am UTC](https://discuss.elastic.co/t/very-slow-search-performance-after-upgrade-to-7-16-1/296152 "2022-02-03T07:02:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Ignacio\_Vera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ignacio_vera/32/36674_2.png) [@Ignacio\_Vera](https://discuss.elastic.co/u/Ignacio_Vera)\
**Post date:** [February 8, 2022, 8:13am UTC](https://discuss.elastic.co/t/very-slow-search-performance-after-upgrade-to-7-16-1/296152/3 "2022-02-08T08:13:49Z")

</div>

I had look into the Lucene [changes](https://github.com/apache/lucene/blob/20f7f33c8d21b94c15887912e80d068970fd095f/lucene/CHANGES.txt#L788) between version 8.9.0 (Elasticsearch 7.15) and 8.10.1 (Elasticsearch 7.16) and there is nothing suspicious that might have cause this.

I am assuming the mapping is the same and data between the two version equivalent. One thing you can try is to run the slower query in a loop and try to capture the hot threads to see if we can see where we are spending most of the time.

Note: It is a bad idea to map a field as an IP if you are going to perform [terms](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/tune-for-search-speed.html#map-ids-as-keyword) queries. It would be much more efficient to map the field as keyword (if you are no going to rum range queries on it).

---

_[View the full topic](https://discuss.elastic.co/t/very-slow-search-performance-after-upgrade-to-7-16-1/296152)._