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

[BUG] ETSCronFlusher high memory consumption and binaries leak #198

Closed
IIILSW opened this issue Apr 27, 2023 · 5 comments
Closed

[BUG] ETSCronFlusher high memory consumption and binaries leak #198

IIILSW opened this issue Apr 27, 2023 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@IIILSW
Copy link

IIILSW commented Apr 27, 2023

Describe the bug
We have registered high memory consumption by the ETSCronFlusher process heap and large number of attached ref binaries.

In the course of our experiments, abandoning the use of Exporter and placing the process in hibernate after cleanup allowed us to reduce memory consumption under load by ~70mb

To Reproduce
Memory consumption increases steadily as the number of metrics and load increases (4k rps in our case)

Expected behavior
A clear and concise description of what you expected to happen.

Environment

  • Elixir version: 1.14.4
  • Erlang/OTP version: 25.3
  • Grafana version: -
  • Prometheus version: -

Additional context
Created PRs in prom_ex and telemetry_metrics_prometheus_core #55

@akoutmos
Copy link
Owner

akoutmos commented May 6, 2023

This may fix the issue and will not require any changes to prometheus_core #200

@akoutmos akoutmos closed this as completed May 7, 2023
@nthouliss
Copy link

Is it possible to get a published version with this patch? I had the same issue and this patch resolved it.

@weisslj
Copy link

weisslj commented Oct 12, 2023

@akoutmos same for us, we would really like to have a new version of prom_ex that includes this bug fix 🙏

@akoutmos
Copy link
Owner

Added this to my todo list for tomorrow! Sorry for the delay!

@akoutmos
Copy link
Owner

It has been done! Download version 1.9.0 for the fix 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants