# MLT Performance Issue with ElasticSearch 1.3.4

**URL:** <https://discuss.elastic.co/t/mlt-performance-issue-with-elasticsearch-1-3-4/20050>\
**Category:** Elasticsearch\
**Created:** [October 2, 2014, 12:20pm UTC](https://discuss.elastic.co/t/mlt-performance-issue-with-elasticsearch-1-3-4/20050 "2014-10-02T12:20:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pir\_Abdul\_Rasool\_Qur](https://avatars.discourse-cdn.com/v4/letter/p/ac91a4/32.png) [@Pir\_Abdul\_Rasool\_Qur](https://discuss.elastic.co/u/Pir_Abdul_Rasool_Qur)\
**Post date:** [October 2, 2014, 12:20pm UTC](https://discuss.elastic.co/t/mlt-performance-issue-with-elasticsearch-1-3-4/20050/1 "2014-10-02T12:20:22Z")

</div>

Hi

ELastic search 1.0.3 was performing better with respect to MLT Api. We are  
witnessing decrease in performance when we upgraded to 1.3.4. Any ideas?

Initially we upgraded to 1.3.3 and then we upgraded to 1.3.4. We also tried  
setting index.translog.flush\_threshold\_size to 1gb but it is still slow as  
compared to what we had in 1.0.3.

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/ca5781d3-c986-4511-9e38-caadc7d3e544%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca5781d3-c986-4511-9e38-caadc7d3e544%40googlegroups.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:58am UTC](https://discuss.elastic.co/t/mlt-performance-issue-with-elasticsearch-1-3-4/20050/2 "2017-07-06T00:58:41Z")

</div>

Closed on July 6, 2017, 12:58am UTC


