# Benchmarking Filebeats

**URL:** <https://discuss.elastic.co/t/benchmarking-filebeats/79746>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 23, 2017, 12:47pm UTC](https://discuss.elastic.co/t/benchmarking-filebeats/79746 "2017-03-23T12:47:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Ravi\_Shanker\_Reddy](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Ravi\_Shanker\_Reddy](https://discuss.elastic.co/u/Ravi_Shanker_Reddy)\
**Post date:** [March 23, 2017, 1:15pm UTC](https://discuss.elastic.co/t/benchmarking-filebeats/79746/3 "2017-03-23T13:15:13Z")

</div>

I copied my script from the same mentioned link.

> [@Filebeat sending data to Logstash seems too slow](https://discuss.elastic.co/t/filebeat-sending-data-to-logstash-seems-too-slow/37596/13):
>
> why not set bulk\_max\_size=2048? I found 4k and 2k much better for throughput in comparison to. with this many workers on physical machine with 16 cores I measured like 45k lines/s. some ways to measure performance and look for bottlenecks: have filebeat publish to console and redirect to /dev/null. Alternatively configure file output in filebeat have filebeat-\>logstash, but configure logstash stdout plugin only with 'dots' codec. Use pv to measure throughput. run filebeat-\>logstash-\>elasticse…

---

_[View the full topic](https://discuss.elastic.co/t/benchmarking-filebeats/79746)._