# How does elasticsearch output affect the logstash pipeline performance?

**URL:** <https://discuss.elastic.co/t/how-does-elasticsearch-output-affect-the-logstash-pipeline-performance/147003>\
**Category:** Logstash\
**Created:** [September 3, 2018, 12:16am UTC](https://discuss.elastic.co/t/how-does-elasticsearch-output-affect-the-logstash-pipeline-performance/147003 "2018-09-03T00:16:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [September 3, 2018, 12:16am UTC](https://discuss.elastic.co/t/how-does-elasticsearch-output-affect-the-logstash-pipeline-performance/147003/1 "2018-09-03T00:16:34Z")

</div>

I have done a benchmarking for _logstash v 6.3.2_ and ask for help interpreting the result.

Benchmarking in logstash under couple of conditions and saw drastic decrease with _Events Emitted Rate_ . All logs were sent from _filebeat_ to _logstash_ .

# Server Condition

1. Filebeat server

- KVM Guest
- OS: RHEL7.4
- CPU Threads: 1
- Memory: 4GB

1. Logstash server

- KVM Guest
- OS: RHEL7.4
- CPU Threads: 1
- Memory: 4GB

# Raw Data condition

1. Blue Circle  
NASA accesslog

2. Red Circle  
[Server Fault (Posts.xml)](https://archive.org/download/stackexchange/serverfault.com.7z)

# Logstash pipeline condition

1. Left Chart

- Input: beats
- Output: file (/dev/null)
- Filter: None

1. Right Chart

- Input: beats
- Output: elasticsearch
- Filter: None

# Result

1. Emitted Rate Result  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/d/0d24320205ffa202f82b5ff22e87680b3b57282a.png)

2. CPU Result  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/0/60e96bc2cb10b928ff96515f8dc1ab02bb87bac8.jpeg)

3. Event Latency  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3be35940f9478c73c826016e7d5b8567fc1f5f43.jpeg)

4. GC duration (jstat)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/c/3cadd7f060c610547443b9ac0ef2844de1fcdcdc.png)

# Question

_Events emitted_ rate has drastically changed when elasticsearch output was used. Since the re was an increase with _Event Latency_ and decrease with _GC duration_ , it looks like events were stucked somewhere between filter or output queue.

Would it be correct to understand the decrease of _Emitted Rate_ was caused by higher latency with network service time for sending bulk requests compared to simple file output ?

I appreciate if I could get advice with clarifying my understanding.

Best Regards,  
Yu Watanabe

---

<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:** [October 1, 2018, 12:16am UTC](https://discuss.elastic.co/t/how-does-elasticsearch-output-affect-the-logstash-pipeline-performance/147003/2 "2018-10-01T00:16:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.