# Elasticsearch indexing performance below expectations at a single installation

**URL:** <https://discuss.elastic.co/t/elasticsearch-indexing-performance-below-expectations-at-a-single-installation/140165>\
**Category:** Elasticsearch\
**Created:** [July 16, 2018, 2:52pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-performance-below-expectations-at-a-single-installation/140165 "2018-07-16T14:52:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)\
**Post date:** [July 16, 2018, 3:34pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-performance-below-expectations-at-a-single-installation/140165/4 "2018-07-16T15:34:42Z")

</div>

we had a bottleneck once, when we updated this to frequently, directly with a script in the logstash -\> elasticsearch pipe ,

> [@Update performance - very low indexing rate](https://discuss.elastic.co/t/update-performance-very-low-indexing-rate/103183/6):
>
> There was a change that affected certain types of update scenarios for ES 5.X as outlined in the [release notes](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/breaking_50_document_api_changes.html#_get_api). This was also discussed in [this thread](https://discuss.elastic.co/t/bulk-updates-are-extremely-slow-after-upgrading-to-5-2/79450/26). Does this match how you are doing updates?

thanks to your support we identified it and built a queue based service, since than, this issue was solved.  
in the test, that inserts bulk messages directly into elasticsearch, without the logstash pipe, the performance is also bad, so i don't think we've got another issue with updates

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-indexing-performance-below-expectations-at-a-single-installation/140165)._