# Tuning to handle extreme initial ingestion conditions (with logstash)

**URL:** https://discuss.elastic.co/t/tuning-to-handle-extreme-initial-ingestion-conditions-with-logstash/188112
**Category:** Elasticsearch
**Created:** [June 28, 2019, 11:02pm UTC](https://discuss.elastic.co/t/tuning-to-handle-extreme-initial-ingestion-conditions-with-logstash/188112 "2019-06-28T23:02:13Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### 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: [June 29, 2019, 6:48am UTC](https://discuss.elastic.co/t/tuning-to-handle-extreme-initial-ingestion-conditions-with-logstash/188112/2 "2019-06-29T06:48:05Z")

</div>

If I recall correctly Logstash file input plugin is single-threaded and can have performance problems when reading very large number of files. Filebeat was created espacially to handle this and can handle this better. I would recommend trying to use Filebeat, which should allow you to have considerably fewer worker threads and a smaller heap for your Logstash instance.

---

_[View the full topic](https://discuss.elastic.co/t/tuning-to-handle-extreme-initial-ingestion-conditions-with-logstash/188112)._