-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Logstash cpu usage fix #2607
Logstash cpu usage fix #2607
Conversation
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shame on me I didn't review this before.
LGTM Thank you @adityacs
* Replace concurrent-ruby-edge with agent lib * Fix logstash cpu consumption * increment gemspec version * increment gemspec version * fix tests Signed-off-by: Cyril Tovena <[email protected]>
Is there an estimation when new version of |
I just did sorry for that. |
What this PR does / why we need it:
Fixes unnecessary cpu usage by logstash. This is happening because
loop select
is expected to block on multiple channels and not just run theloop
indefinitely. Looks likeconcurrent-ruby
library is not handling this. Also, tried agent but even this library is not handling channel block and receive as expected. So, changed the implementation to handle concurrency using just Ruby Threads.Which issue(s) this PR fixes:
Fixes #2551
After the initial startup, CPU usage is minimal