# Filebeat high memory usage v6.4.2

**URL:** <https://discuss.elastic.co/t/filebeat-high-memory-usage-v6-4-2/155186>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 2, 2018, 3:25pm UTC](https://discuss.elastic.co/t/filebeat-high-memory-usage-v6-4-2/155186 "2018-11-02T15:25:07Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [November 2, 2018, 5:16pm UTC](https://discuss.elastic.co/t/filebeat-high-memory-usage-v6-4-2/155186/5 "2018-11-02T17:16:01Z")

</div>

Hi @grantk

For debugging purposes, it might be useful to know the general structure of the JSON files you are using. I mean, 200 entries/json but how big they are, how many keys they could have or if they are multiline or single line.

A couple of things you can try tweaking are the [internal queue](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-internal-queue.html), specially the [min events value](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-internal-queue.html#_literal_flush_min_events_literal) and the [harvester buffer size](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-log.html#_literal_harvester_buffer_size_literal)

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-high-memory-usage-v6-4-2/155186)._