# Which is better for phrase suggestions?

**URL:** <https://discuss.elastic.co/t/which-is-better-for-phrase-suggestions/51594>\
**Category:** Elasticsearch\
**Created:** [June 1, 2016, 5:09pm UTC](https://discuss.elastic.co/t/which-is-better-for-phrase-suggestions/51594 "2016-06-01T17:09:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![automotiveace](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@automotiveace](https://discuss.elastic.co/u/automotiveace)\
**Post date:** [June 1, 2016, 5:09pm UTC](https://discuss.elastic.co/t/which-is-better-for-phrase-suggestions/51594/1 "2016-06-01T17:09:07Z")

</div>

It seems I can use the combo of a shingles filter and tokenizer to create a multi-word (phrase) autocomplete feature using a multi-match query. However it also looks like I can use the Completion suggester for basically the same purpose. If I have mostly 2,3 or 4 word phrases that make up the suggestions, how big of an index can I make before the Completion suggester performance degrades. It seems that is the whole purpose behind the Completions suggester - speed.

I plan to use a separate index for the autocomplete feature.

---

<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:47pm UTC](https://discuss.elastic.co/t/which-is-better-for-phrase-suggestions/51594/2 "2017-07-05T22:47:11Z")

</div>

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