# Bad GELF performance

**URL:** <https://discuss.elastic.co/t/bad-gelf-performance/142933>\
**Category:** Logstash\
**Created:** [August 3, 2018, 3:09pm UTC](https://discuss.elastic.co/t/bad-gelf-performance/142933 "2018-08-03T15:09:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hangstl](https://avatars.discourse-cdn.com/v4/letter/h/f17d59/32.png) [@hangstl](https://discuss.elastic.co/u/hangstl)\
**Post date:** [August 3, 2018, 3:09pm UTC](https://discuss.elastic.co/t/bad-gelf-performance/142933/1 "2018-08-03T15:09:05Z")

</div>

I have a Graylog installation that can handle well over 25.000 msg/sec.

I am now experimenting with setting up a dedicated Logstash cluster. So something like this:  
Filebeat (n hosts) -\> Logstash Cluster -\> Graylog

The biggest issue now is that I can not send more than 2.500 msg/sec from **one** host to Graylog. No matter how big the host is (4, 8, 16, ... CPUs), no matter how small the messages are, there is always this 2.500 msg/seg limit.

I've even created messages with only 1 Byte paylog, the limit here is 2.800 msg/sec.

I can send messages from, for example, 4 different hosts. Resulting in 10.000 msg/sec (4 x 2.500). Graylog can handle this easily.

So my question is: Why can **one** host send no more than 2.500 msg/sec via GELF?

---

<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:** [August 31, 2018, 3:09pm UTC](https://discuss.elastic.co/t/bad-gelf-performance/142933/2 "2018-08-31T15:09:06Z")

</div>

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