# Autocomplete performance improvements

**URL:** <https://discuss.elastic.co/t/autocomplete-performance-improvements/107304>\
**Category:** Elasticsearch\
**Created:** [November 12, 2017, 2:06pm UTC](https://discuss.elastic.co/t/autocomplete-performance-improvements/107304 "2017-11-12T14:06:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikevic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikevic/32/24104_2.png) [@mikevic](https://discuss.elastic.co/u/mikevic)\
**Post date:** [November 12, 2017, 2:06pm UTC](https://discuss.elastic.co/t/autocomplete-performance-improvements/107304/1 "2017-11-12T14:06:37Z")

</div>

I have an index with about 2M records that is currently really hurting the CPU, when autocomplete queries are sent.

I was looking at creating a new index just for autocomplete and seeding just the names instead of the having the entire object (which is quite large) in the index.

In theory, would this speed up the autocomplete and stop hurting the CPU so much?

---

<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:** [December 10, 2017, 2:11pm UTC](https://discuss.elastic.co/t/autocomplete-performance-improvements/107304/2 "2017-12-10T14:11:35Z")

</div>

Closed on December 10, 2017, 2:11pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.