# Distributed Frequency Search

**URL:** <https://discuss.elastic.co/t/distributed-frequency-search/20580>\
**Category:** Elasticsearch\
**Created:** [November 5, 2014, 1:44pm UTC](https://discuss.elastic.co/t/distributed-frequency-search/20580 "2014-11-05T13:44:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sofiane\_Cherchalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sofiane_cherchalli/32/1129_2.png) [@Sofiane\_Cherchalli](https://discuss.elastic.co/u/Sofiane_Cherchalli)\
**Post date:** [November 5, 2014, 1:44pm UTC](https://discuss.elastic.co/t/distributed-frequency-search/20580/1 "2014-11-05T13:44:14Z")

</div>

According to  
[http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/relevance-is-broken.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/relevance-is-broken.html),  
the relevance is broken until we have enough data distributed uniformly  
across shards.

My question is: If I initially use the ?search\_type=dfs\_query\_then\_fetch  
parameter because I few data, will it affect the performance when the  
Production environment will have enough data sharded uniformly?

Thanks.

--  
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/50856f05-4329-4001-a833-6c568fc5730f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/50856f05-4329-4001-a833-6c568fc5730f%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Sofiane\_Cherchalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sofiane_cherchalli/32/1129_2.png) [@Sofiane\_Cherchalli](https://discuss.elastic.co/u/Sofiane_Cherchalli)\
**Post date:** [November 5, 2014, 1:55pm UTC](https://discuss.elastic.co/t/distributed-frequency-search/20580/2 "2014-11-05T13:55:50Z")

</div>

Answering myself:

According to ES blog  
[http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/](http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/)  
there is performance hit. It would be nice to have a feature that triggers  
automatically DFS based on a kinda threshold...

On Wednesday, November 5, 2014 2:44:14 PM UTC+1, Sofiane Cherchalli wrote:

> According to  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/relevance-is-broken.html),  
> the relevance is broken until we have enough data distributed uniformly  
> across shards.
> 
> My question is: If I initially use the ?search\_type=dfs\_query\_then\_fetch  
> parameter because I few data, will it affect the performance when the  
> Production environment will have enough data sharded uniformly?
> 
> Thanks.

--  
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/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [November 6, 2014, 3:34pm UTC](https://discuss.elastic.co/t/distributed-frequency-search/20580/3 "2014-11-06T15:34:53Z")

</div>

We did some performance testing and found that the performance hit from  
using DFS was minor.

--  
Ivan

On Wed, Nov 5, 2014 at 8:55 AM, Sofiane Cherchalli [sofianito@gmail.com](mailto:sofianito@gmail.com)  
wrote:

> Answering myself:
> 
> According to ES blog  
> [http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/](http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/)  
> there is performance hit. It would be nice to have a feature that triggers  
> automatically DFS based on a kinda threshold...
> 
> On Wednesday, November 5, 2014 2:44:14 PM UTC+1, Sofiane Cherchalli wrote:
> 
> > According to [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/)  
> > current/relevance-is-broken.html, the relevance is broken until we have  
> > enough data distributed uniformly across shards.
> > 
> > My question is: If I initially use the ?search\_type=dfs\_query\_then\_fetch  
> > parameter because I few data, will it affect the performance when the  
> > Production environment will have enough data sharded uniformly?
> > 
> > Thanks.
> 
> --  
> 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/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CALY%3DcQCLCajraVb2VkY%3DsTLofJhYp1OCSz2QtkA603JJfrHgHw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCLCajraVb2VkY%3DsTLofJhYp1OCSz2QtkA603JJfrHgHw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:51am UTC](https://discuss.elastic.co/t/distributed-frequency-search/20580/4 "2017-07-06T00:51:45Z")

</div>


