# Logstash performance

**URL:** <https://discuss.elastic.co/t/logstash-performance/50109>\
**Category:** Logstash\
**Created:** [May 16, 2016, 11:13am UTC](https://discuss.elastic.co/t/logstash-performance/50109 "2016-05-16T11:13:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maher\_Ben\_Taleb\_Ali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maher_ben_taleb_ali/32/26774_2.png) [@Maher\_Ben\_Taleb\_Ali](https://discuss.elastic.co/u/Maher_Ben_Taleb_Ali)\
**Post date:** [May 16, 2016, 11:13am UTC](https://discuss.elastic.co/t/logstash-performance/50109/1 "2016-05-16T11:13:46Z")

</div>

We are trying to deploy logstash in production.

So I need a detailed answer for these questions:

-Logstash extracts data from database using SQL. How exactly logstash get notified about new data?  
-Is there a way to configure how logstash search new data?  
We cannot rely on this kind of abstraction (even if it maybe optimum)

-is there any official performance reports that I can check?  
We are going to make our personal tests, but it’s still good to have a first impression.

Thanks!!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 17, 2016, 6:11am UTC](https://discuss.elastic.co/t/logstash-performance/50109/2 "2016-05-17T06:11:31Z")

</div>

[https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jdbc.html#\_state](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jdbc.html#_state)

And no, we don't provide any sort of performance metrics around LS sorry.

---

<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:57am UTC](https://discuss.elastic.co/t/logstash-performance/50109/3 "2017-07-06T04:57:28Z")

</div>

Closed on July 6, 2017, 4:57am UTC


