# Pathetic Logstash performance using UDP input and Redis output

**URL:** https://discuss.elastic.co/t/pathetic-logstash-performance-using-udp-input-and-redis-output/34409
**Category:** Logstash
**Created:** [November 12, 2015, 12:30pm UTC](https://discuss.elastic.co/t/pathetic-logstash-performance-using-udp-input-and-redis-output/34409 "2015-11-12T12:30:01Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![venkaty](https://avatars.discourse-cdn.com/v4/letter/v/919ad9/32.png) [@venkaty](https://discuss.elastic.co/u/venkaty)
#### Post date: [November 12, 2015, 12:30pm UTC](https://discuss.elastic.co/t/pathetic-logstash-performance-using-udp-input-and-redis-output/34409/1 "2015-11-12T12:30:01Z")

</div>

Following is the log-stash configuration used for capturing the events from various nodes streaming syslog events and the events are buffered in Redis queue for processing.

input {  
udp  
{  
port =\> 514  
buffer\_size =\> 32768  
queue\_size =\> 300000  
workers =\> 10  
}  
}

output {  
redis {  
host =\> '10.1.0.16'  
data\_type =\> 'list'  
key =\> 'events'  
port =\> 6379  
batch =\> true  
batch\_events =\> 1000  
batch\_timeout =\> 5  
workers =\> 10  
}  
}

With above configuration, we have achieved 800 EPS without UDP data loss.

In our test environment, Logstash 2.0 is deployed on win8 64 bit, i7 2.6 GHz, 8 GB RAM.

Please share your thoughts to improve processing of events at 50 K events per sec without data loss.  
Also suggest the ideal system hardware for such a scenario.

---

<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, 5:23am UTC](https://discuss.elastic.co/t/pathetic-logstash-performance-using-udp-input-and-redis-output/34409/2 "2017-07-06T05:23:05Z")

</div>