# Logstash performance degradation after upgrade

**URL:** <https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817>\
**Category:** Logstash\
**Created:** [June 3, 2016, 5:55pm UTC](https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817 "2016-06-03T17:55:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dkota](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dkota](https://discuss.elastic.co/u/dkota)\
**Post date:** [June 3, 2016, 5:55pm UTC](https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817/1 "2016-06-03T17:55:16Z")

</div>

we were getting 60-80K indexing rate in our production cluster, after upgrading the cluster (from v 2.2.2) we had this go down to 12-14K.

Elasticsearch 2.3.1  
Logstash 2.3.1  
Marvel 2.3.1  
Shield 2.3.1  
Kibana 4.5.0

There is no change in any of config files. Is there a change in the logstash uses resources from 2.2.2 to 2.3.1

No information in the logs even in --debug mode

Any help in this direction is appreciated.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 8, 2016, 5:36am UTC](https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817/2 "2016-06-08T05:36:06Z")

</div>

Looking at the [2.3 release notes](https://www.elastic.co/guide/en/logstash/2.3/releasenotes.html) this bullet stands out:

> Reverted default output workers to 1. Previously we had made output workers the same as number of pipeline workers (#4877).

---

<div class="post-metadata">

**Author:** ![dkota](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dkota](https://discuss.elastic.co/u/dkota)\
**Post date:** [June 8, 2016, 6:09pm UTC](https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817/3 "2016-06-08T18:09:03Z")

</div>

yes..That was the issue

---

<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, 4:54am UTC](https://discuss.elastic.co/t/logstash-performance-degradation-after-upgrade/51817/4 "2017-07-06T04:54:06Z")

</div>