# Logstash & Redis **URL:** https://discuss.elastic.co/t/logstash-redis/33332 **Category:** Logstash **Created:** [October 30, 2015, 3:30am UTC](https://discuss.elastic.co/t/logstash-redis/33332 "2015-10-30T03:30:14Z") **Posts on this page:** 5 **Page:** 1
### Author: ![genebean](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/genebean/32/5565_2.png) [@genebean](https://discuss.elastic.co/u/genebean) #### Post date: [October 30, 2015, 3:30am UTC](https://discuss.elastic.co/t/logstash-redis/33332/1 "2015-10-30T03:30:14Z")
Can anyone suggest a way to read entries from Redis faster? I seem to be inserting them faster than I can read them as I have 8 Logstash indexers running and either they can't read fast enough or there is a bottleneck that I am not aware somewhere else in Logstash that is slowing down the ingestion rate. Any help would be appreciated. ---
### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist) #### Post date: [October 30, 2015, 3:34am UTC](https://discuss.elastic.co/t/logstash-redis/33332/2 "2015-10-30T03:34:28Z")
Have you benchmarked your downstream system(s), e.g. Elasticsearch, to verify that that is not what is limiting throughput? If so, what does your configuration look like? ---
### Author: ![genebean](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/genebean/32/5565_2.png) [@genebean](https://discuss.elastic.co/u/genebean) #### Post date: [October 30, 2015, 11:29am UTC](https://discuss.elastic.co/t/logstash-redis/33332/3 "2015-10-30T11:29:12Z")
I have not... can you recommend how to do that? ---
### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist) #### Post date: [October 30, 2015, 5:04pm UTC](https://discuss.elastic.co/t/logstash-redis/33332/4 "2015-10-30T17:04:09Z")
The easiest way might be to generate a number of large files containing data in the format you receive from Redis and then use the file input to load this into Elasticsearch as quickly as possible while monitoring Elasticsearch. Use the same number of Logstash processes and make sure to set filter workers to an appropriate value if you have not already done this. The file input is quite efficient and if this gives you the same indexing throughout as with Redis, it is likely that the bottleneck may not be Redis at all. ---
### 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:24am UTC](https://discuss.elastic.co/t/logstash-redis/33332/5 "2017-07-06T05:24:50Z")