# Filebeat perf benchmark numbers
**URL:** https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247
**Category:** Beats
**Tags:** filebeat
**Created:** [July 15, 2017, 1:18am UTC](https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247 "2017-07-15T01:18:42Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@vramakrishnan](https://discuss.elastic.co/u/vramakrishnan)
#### Post date: [July 15, 2017, 1:18am UTC](https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247/1 "2017-07-15T01:18:43Z")
I am looking for Filebeat performance benchmark numbers and how it compares other shippers like FluentD.
Any pointers would help.
---
### Author:  [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [July 17, 2017, 8:34am UTC](https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247/2 "2017-07-17T08:34:03Z")
In our experience Filebeat is rarely the bottleneck. It's either the next stage (Logstash / Elasticsearch / Kafka, etc.), or the network, or the disk throughput.
If you want, you can benchmark Filebeat in isolation by using the file output, or the console output redirected to `/dev/null`. FIlebeat prints some stats every 30 seconds. The number you will get depends on your hardware, we see above 100K per second on good HW. But as Filebeat never runs in isolation, this will be just the upper limit of what you can get in practice.
---
### Author:  [@vramakrishnan](https://discuss.elastic.co/u/vramakrishnan)
#### Post date: [July 18, 2017, 2:02am UTC](https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247/3 "2017-07-18T02:02:16Z")
Thanks.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 15, 2017, 2:02am UTC](https://discuss.elastic.co/t/filebeat-perf-benchmark-numbers/93247/4 "2017-08-15T02:02:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.