# Wildcard Query followed by Heap/CPU spike

**URL:** <https://discuss.elastic.co/t/wildcard-query-followed-by-heap-cpu-spike/62648>\
**Category:** Elasticsearch\
**Created:** [October 10, 2016, 4:49pm UTC](https://discuss.elastic.co/t/wildcard-query-followed-by-heap-cpu-spike/62648 "2016-10-10T16:49:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![EuclideanSearch](https://avatars.discourse-cdn.com/v4/letter/e/c77e96/32.png) [@EuclideanSearch](https://discuss.elastic.co/u/EuclideanSearch)\
**Post date:** [October 10, 2016, 4:49pm UTC](https://discuss.elastic.co/t/wildcard-query-followed-by-heap-cpu-spike/62648/1 "2016-10-10T16:49:49Z")

</div>

Hi,

We are performing a wildcard query over some fields and (after the query returned, which did not take much time) saw the CPU and Heap spike. From [https://github.com/elastic/elasticsearch/issues/8249](https://github.com/elastic/elasticsearch/issues/8249) I think this is due to caching of the wildcard query. So:

1. Does that conclusion seem reasonable
2. How to disable caching?

Thank you,  
EuclideanSearch

---

<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, 10:13pm UTC](https://discuss.elastic.co/t/wildcard-query-followed-by-heap-cpu-spike/62648/2 "2017-07-05T22:13:35Z")

</div>

Closed on July 5, 2017, 10:13pm UTC