# Read slow for large files in S3?

**URL:** <https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551>\
**Category:** Logstash\
**Created:** [September 27, 2016, 3:57am UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551 "2016-09-27T03:57:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)\
**Post date:** [September 27, 2016, 3:57am UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/1 "2016-09-27T03:57:57Z")

</div>

I have two files in a folder, one small 300kb, and one large, 2G. Logstash only reads 300kb one. Is it right? Shall i wait more time?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 28, 2016, 5:43am UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/2 "2016-09-28T05:43:38Z")

</div>

Is there any indication of network activity, suggesting that it's still working on the 2 GB file? If you bump up logging by starting Logstash with `--debug`, do the logs indicate that the download is even starting?

---

<div class="post-metadata">

**Author:** ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)\
**Post date:** [September 28, 2016, 11:41pm UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/3 "2016-09-28T23:41:55Z")

</div>

Thanks! It keeps saying:  
**Pushing flush onto pipeline {:level=\>:debug, :file=\>"logstash/pipeline.rb", :line=\>"458", :method=\>"flush"}**

Does it mean it is downloading the file to my local ram?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 29, 2016, 5:29am UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/4 "2016-09-29T05:29:19Z")

</div>

S3 files are never downloaded into RAM. But no, that message isn't interesting.

---

<div class="post-metadata">

**Author:** ![Allie\_Yang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allie_yang/32/16538_2.png) [@Allie\_Yang](https://discuss.elastic.co/u/Allie_Yang)\
**Post date:** [September 29, 2016, 4:59pm UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/5 "2016-09-29T16:59:06Z")

</div>

Oh Sorry would you elaborate what does that message mean? what is being flushed into pipeline?

---

<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:36am UTC](https://discuss.elastic.co/t/read-slow-for-large-files-in-s3/61551/6 "2017-07-06T04:36:25Z")

</div>