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 of kubernetes_metadata_filter plugin #179
Comments
Version:root@fd-log-router-8mqzw:/home/fluent# fluentd --version Logs:{"log":"2019-06-07 13:10:47 +0000 [info]: #0 plugin:out_flowcounter_simple\u0009count:1\u0009indicator:num\u0009unit:second\n","stream":"stdout","time":"2019-06-07T13:10:47.042130594Z"} |
I don't know about any performance measurement data available for this plugin. I'm not familiar with ruby performance measurement. Any help would be appreciated. |
related to #39 |
Closing in lieu of merging #347 where was able to identify some valuable changes |
Hi,
Wanted to know if there is any performance measurement data available for this plugin anywhere.
Did anyone faced any performance issues running this in fluentd?
What we have noticed in our testing running this plugin is not at all encouraging.
We were testing performance of fluentd which runs as a daemon in a k8s cluster based on fluent/fluentd-benchmark and it gave almost the numbers it promised but the moment we added kubernetes_metadata_filter plugin, the performance significantly went down.
Setup:
Application writes logs at 20k lines per second which is read by fluentd using tail and then displays the msg per second count.
Outcome:
Without kubernetes_metadata_filter, fluentd was able to read at the same rate which is 20k lines per sec, but with kubernetes_metadata_filter added in config, it comes down to 4k lines per second. This is in single worker setup.
Config:
The text was updated successfully, but these errors were encountered: