# Packetbeat performance

**URL:** https://discuss.elastic.co/t/packetbeat-performance/46834
**Category:** Beats
**Tags:** packetbeat
**Created:** [April 8, 2016, 4:49pm UTC](https://discuss.elastic.co/t/packetbeat-performance/46834 "2016-04-08T16:49:32Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [April 11, 2016, 3:53pm UTC](https://discuss.elastic.co/t/packetbeat-performance/46834/6 "2016-04-11T15:53:55Z")

</div>

So you have like 50 transactions per second in elasticsearch, not packetbeat only processing 50 packets per second. Maybe it's a problem with indexing performance in elasticsearch. Have you tried to increase `bulk_max_size: ...` in elasticsearch output? Default size for ES is 50. If ES can not index fast enough, packetbeat will drop transaction events.

[Here are some tips for getting stats about filebeat output](https://discuss.elastic.co/t/filebeat-sending-data-to-logstash-seems-too-slow/37596/13). The same script and `httpprof` option works for packetbeat as well.

---

_[View the full topic](https://discuss.elastic.co/t/packetbeat-performance/46834)._