# Filebeat performance issue

**URL:** https://discuss.elastic.co/t/filebeat-performance-issue/86558
**Category:** Beats
**Tags:** filebeat
**Created:** [May 21, 2017, 6:43am UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558 "2017-05-21T06:43:18Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![kalman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kalman/32/49563_2.png) [@kalman](https://discuss.elastic.co/u/kalman)
#### Post date: [May 21, 2017, 6:43am UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558/1 "2017-05-21T06:43:18Z")

</div>

I'm using filebeat 5.4.4 on windows to harvest from log file directly to elastic stack, the requirement is that the logs come in to elastic as soon as possible (near real-time).  
for some reson the logs only show up in kibana about 5 seconds later, after the events come in the last one comes in with a additional delay of a second

my filebeat cofig:

```
filebeat.prospectors:
- input_type: log
  paths:
    - C:\var\log\*.log

    exclude_lines: ["^}"]
   fields:
      Host: myhost
   fields_under_root: true
filebeat.idle_timeout: 500ms
output.elasticsearch:
  hosts: ["localhost:9200"]
  index: "my-index-%{+yyyy.MM.dd}"
  pipeline: my_pipeline
  template.name: "my_template"
  template.enabled: true
```

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [May 22, 2017, 1:19pm UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558/2 "2017-05-22T13:19:22Z")

</div>

Have a look at the backoff variables: [https://www.elastic.co/guide/en/beats/filebeat/5.4/configuration-filebeat-options.html#\_backoff](https://www.elastic.co/guide/en/beats/filebeat/5.4/configuration-filebeat-options.html#_backoff)

---

<div class="post-metadata">

### Author: ![kalman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kalman/32/49563_2.png) [@kalman](https://discuss.elastic.co/u/kalman)
#### Post date: [May 23, 2017, 9:53am UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558/3 "2017-05-23T09:53:58Z")

</div>

thank you for the replay, I saw some difference in performance  
Is there a recommended setting that is recommended for events to come in near real time and not make the system overload

I set the backoff to 500ms  
and max\_backoff to 2s

can I set max\_backoff to 500ms?

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [May 23, 2017, 1:57pm UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558/4 "2017-05-23T13:57:58Z")

</div>

I would not recommend a backoff \< 1s but there is no lower limit. As you mentioned correctly, the lower the number the higher the overhead. Best test it on your system on how far you can go ...

---

<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: [June 20, 2017, 1:58pm UTC](https://discuss.elastic.co/t/filebeat-performance-issue/86558/5 "2017-06-20T13:58:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
