# Overhead of Completion Suggester

**URL:** <https://discuss.elastic.co/t/overhead-of-completion-suggester/14857>\
**Category:** Elasticsearch\
**Created:** [December 13, 2013, 3:35pm UTC](https://discuss.elastic.co/t/overhead-of-completion-suggester/14857 "2013-12-13T15:35:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tim_s/32/958_2.png) [@Tim\_S](https://discuss.elastic.co/u/Tim_S)\
**Post date:** [December 13, 2013, 3:35pm UTC](https://discuss.elastic.co/t/overhead-of-completion-suggester/14857/1 "2013-12-13T15:35:27Z")

</div>

The completion suggester uses payloads (which will presumably use extra  
space on disk) and specifies its own set of analyzers (presumably  
suggesting that the terms are analyzed a second time).

Therefore I assume if I enable the completion suggester for a bunch of  
fields, it will use more disk space. Does anyone have any idea how much  
more?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/00da9cfe-95bc-4c28-9cab-14a38fb9b2a0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/00da9cfe-95bc-4c28-9cab-14a38fb9b2a0%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [December 13, 2013, 3:46pm UTC](https://discuss.elastic.co/t/overhead-of-completion-suggester/14857/2 "2013-12-13T15:46:53Z")

</div>

Hey,

be aware, that the completion suggester not only needs disk space, but also  
resides in memory (the secret of its speed). Thats why there is a stats API  
for completion stats. This is also the reason, that you should thrive for a  
minimum payload, as this can explode the size of the completion data  
tremendeously.

That said, trying out and checking seems to be the most viable option.

Links:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

--Alex

On Fri, Dec 13, 2013 at 4:35 PM, Tim S [timstibbs@gmail.com](mailto:timstibbs@gmail.com) wrote:

> The completion suggester uses payloads (which will presumably use extra  
> space on disk) and specifies its own set of analyzers (presumably  
> suggesting that the terms are analyzed a second time).
> 
> Therefore I assume if I enable the completion suggester for a bunch of  
> fields, it will use more disk space. Does anyone have any idea how much  
> more?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/00da9cfe-95bc-4c28-9cab-14a38fb9b2a0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/00da9cfe-95bc-4c28-9cab-14a38fb9b2a0%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8r3hNJDp\_%3D\_ZGY6z2SaCCoBLD90fPiLMjsh4Yr4ry%2BDA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8r3hNJDp_%3D_ZGY6z2SaCCoBLD90fPiLMjsh4Yr4ry%2BDA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:01am UTC](https://discuss.elastic.co/t/overhead-of-completion-suggester/14857/3 "2017-07-06T02:01:18Z")

</div>


