# Understanding DEBUG lines - Tuning Opportunity?
**URL:** https://discuss.elastic.co/t/understanding-debug-lines-tuning-opportunity/48345
**Category:** Beats
**Tags:** filebeat
**Created:** [April 25, 2016, 6:47pm UTC](https://discuss.elastic.co/t/understanding-debug-lines-tuning-opportunity/48345 "2016-04-25T18:47:27Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@gcherneski](https://discuss.elastic.co/u/gcherneski)
#### Post date: [April 25, 2016, 6:47pm UTC](https://discuss.elastic.co/t/understanding-debug-lines-tuning-opportunity/48345/1 "2016-04-25T18:47:27Z")
I have debug turned up on my filebeat (1.2.0-x86-64) and wanted to know if the following log lines are an indication of a tuning opportunity:
**2016-04-25T18:34:13Z DBG output worker: publish 2048 events**
**2016-04-25T18:34:13Z DBG Try to publish 2048 events to logstash with window size 1024**
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [April 25, 2016, 10:19pm UTC](https://discuss.elastic.co/t/understanding-debug-lines-tuning-opportunity/48345/2 "2016-04-25T22:19:03Z")
just seeing these 2 messages is kind of out of context. without complete log I can not tell what's exactly happening. The window size does grow starting at 10 up to bulk\_max\_size. If logstash stops responding, the window-size will stop growing and might shrink instead.
Somewhat related: [Logstash output load balancing and workers settings](https://discuss.elastic.co/t/logstash-output-load-balancing-and-workers-settings/48176)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:52pm UTC](https://discuss.elastic.co/t/understanding-debug-lines-tuning-opportunity/48345/3 "2017-07-05T21:52:47Z")