# 200 logs/minute elastic performance

**URL:** <https://discuss.elastic.co/t/200-logs-minute-elastic-performance/61258>\
**Category:** Elasticsearch\
**Created:** [September 22, 2016, 1:11pm UTC](https://discuss.elastic.co/t/200-logs-minute-elastic-performance/61258 "2016-09-22T13:11:45Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rubpa](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rubpa](https://discuss.elastic.co/u/rubpa)\
**Post date:** [September 30, 2016, 8:50am UTC](https://discuss.elastic.co/t/200-logs-minute-elastic-performance/61258/4 "2016-09-30T08:50:58Z")

</div>

From [here](https://discuss.elastic.co/t/interpreting-output-of-logstash-metrics-filter/40284) and the linked github bug, I understand that the rate I'm getting is around 200 logs/second and _not_ 200 logs/minute as I wrote in the title.

I have also confirmed with various tests that the bottleneck is elasticsearch and not logstash. I'm now trying out this: [https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html)

---

_[View the full topic](https://discuss.elastic.co/t/200-logs-minute-elastic-performance/61258)._