# Indexing speed in ES v1.71 approx 18% slower than v1.4.5 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 31, 2015, 2:52am UTC](https://discuss.elastic.co/t/indexing-speed-in-es-v1-71-approx-18-slower-than-v1-4-5/28323 "2015-08-31T02:52:43Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\ **Post date:** [September 2, 2015, 12:01pm UTC](https://discuss.elastic.co/t/indexing-speed-in-es-v1-71-approx-18-slower-than-v1-4-5/28323/13 "2015-09-02T12:01:59Z")
Hmm my response (via email) was truncated for some reason ... trying again: I think (not certain) for logstash it's the number of workers you specify for the Elasticsearch output? I think the default is 1: [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html) Or in your custom Go client, you would control how many threads (goroutines?) are sending bulk indexing requests concurrently. You can ask for node stats, then look under thread\_pool -\> bulk -\> active to see how many bulk threads are currently working, but this isn't a precise measure since when you check, it could be your client side threads had just received results and are working to prepare the next request and so they are not counted. You want to have enough client side concurrency so the server side resources are saturated (either CPU or IO or, if you're lucky, both!). --- _[View the full topic](https://discuss.elastic.co/t/indexing-speed-in-es-v1-71-approx-18-slower-than-v1-4-5/28323)._