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

High memory usage by jmx_exporter when connecting to Kafka #900

Closed
i4yyds opened this issue Dec 15, 2023 · 1 comment
Closed

High memory usage by jmx_exporter when connecting to Kafka #900

i4yyds opened this issue Dec 15, 2023 · 1 comment

Comments

@i4yyds
Copy link

i4yyds commented Dec 15, 2023

Hi,
I'm using jmx_exporter to connect to Kafka, and I noticed that it is consuming a significant amount of memory, around 600MB. I'm wondering why it requires such a large amount of memory.
I have considered a few factors that could contribute to this high memory usage, such as the number of MBeans being monitored, the size of exported metric values, and the export frequency. However, I would appreciate some insights from the Prometheus team regarding any specific reasons or potential optimizations for reducing the memory footprint of jmx_exporter in this scenario.
Could you please shed some light on why jmx_exporter might be consuming this much memory and provide any suggestions or best practices for optimizing its memory usage?
Thank you for your assistance!
Best regards,

@dhoard
Copy link
Collaborator

dhoard commented Dec 19, 2023

See #685 (comment)

Depending on your Kafka rules, this could be large.

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

2 participants