# How to decide an optimal settings for workers? **URL:** \ **Category:** Logstash\ **Created:** [March 22, 2016, 3:03am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061 "2016-03-22T03:03:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zpp](https://avatars.discourse-cdn.com/v4/letter/z/54ee81/32.png) [@zpp](https://discuss.elastic.co/u/zpp)\ **Post date:** [March 22, 2016, 3:03am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/1 "2016-03-22T03:03:50Z")
For logstash ElasticSearch output plugin, how to determine the proper number of workers to use? If I play around the settings, is there a way to know whether the performance is getting better (or worse?) ---
**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:** [March 22, 2016, 6:48am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/2 "2016-03-22T06:48:49Z")
> For logstash Elasticsearch output plugin, how to determine the proper number of workers to use? Measure the throughput for a typical workload. Marvel or another cluster monitoring tool should be helpful here. > If I play around the settings, is there a way to know whether the performance is getting better (or worse?) If there was no way of knowing whether the performance was better or worse, would it even matter? ---
**Author:** ![zpp](https://avatars.discourse-cdn.com/v4/letter/z/54ee81/32.png) [@zpp](https://discuss.elastic.co/u/zpp)\ **Post date:** [March 22, 2016, 6:52am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/3 "2016-03-22T06:52:23Z")
"Measure the throughput for a typical workload. Marvel or another cluster monitoring tool should be helpful here" can you elaborate a bit more on how to? ---
**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:** [March 22, 2016, 7:01am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/4 "2016-03-22T07:01:32Z")
I'm not sure what to elaborate on. This should be pretty straight forward. Use e.g. Marvel to inspect the indexing throughput while you feed Logstash with lots of data. Experiment with different configuration options. Keep in mind that ES itself might be a bottleneck, so it's totally possible that you'll get the same throughput regardless of the LS settings. ---
**Author:** ![zpp](https://avatars.discourse-cdn.com/v4/letter/z/54ee81/32.png) [@zpp](https://discuss.elastic.co/u/zpp)\ **Post date:** [March 22, 2016, 7:28am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/5 "2016-03-22T07:28:39Z")
I see.. thank you. Reason I'm asking this question is that I just upgraded my ELK cluster to latest version, and I noticed a few things: 1\> there is some slow down in indexing, i.e. data is queued at Redis, and I was wondering whether increasing workers can improve the performance. 2\> there are warnings " retrying failed action with response code: 429" on and off at indexers, which I don't observe previously. Is this expected with the newer version? or it must caused by other factors? ---
**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, 5:05am UTC](https://discuss.elastic.co/t/how-to-decide-an-optimal-settings-for-workers/45061/6 "2017-07-06T05:05:59Z")
Closed on July 6, 2017, 5:05am UTC