Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Performance] Improve Syslog Input Connection Performance #72

Open
kaisecheng opened this issue Apr 18, 2023 · 2 comments
Open

[Performance] Improve Syslog Input Connection Performance #72

kaisecheng opened this issue Apr 18, 2023 · 2 comments

Comments

@kaisecheng
Copy link

kaisecheng commented Apr 18, 2023

This plugin creates a new thread to handle a new connection. This is not the best use of the resources, especially when there is a high number of connections, the CPU usage increases significantly.

beats-input uses Netty server to handle connection. Changing thread-based connections to NIO would be the right way to go.

@roaksoax
Copy link

There's been recent reports that after upgrading to latest version of Logstash, that CPU usage increases even with the lack of performance improvement on this area.

As part of this, we shoul.d investigate whether this problem is being made worse by Jruby,.

@roaksoax roaksoax changed the title improve tcp connection performance improve connection performance Apr 21, 2023
@roaksoax roaksoax changed the title improve connection performance Improve Connection Performance Apr 21, 2023
@roaksoax roaksoax changed the title Improve Connection Performance Improve Syslog Input Connection Performance Apr 21, 2023
@roaksoax roaksoax changed the title Improve Syslog Input Connection Performance [Performance] Improve Syslog Input Connection Performance Apr 21, 2023
@iamhowardtheduck
Copy link

This is affecting one of my customers and we are actively looking for updates. The current suggestion from support is to downgrade and I also discussed migrating to Elastic ingest pipelines since this is just basic syslog ingestion coupled with custom parsing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants