You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The profiling information available with #446 shows clearly that the issue is related to the implementation done in #359. After removing the correlation between metrics and traces, everything is stable and there are no memory consumption issues any more.
The image above shows also clearly how the update of the above said implementation (removing of the correlation) stabilized the situation
Preflight checklist
Describe the bug
Each and every request to heimdall increases the memory consumption by a small portion.
How can the bug be reproduced
To be able to properly observe the memory consuption, you'll need an observability stack, like e.g. provided by grafana, prometheus and loki
helm install heimdall --namespace heimdall --create-namespace --set demo.enable=true dadrus/heimdall
for i in {1..100000}; do curl -H "Host: demo-app" 127.0.0.1/heimdall-demo/anonymous; done
Relevant log output
No response
Relevant configuration
No response
Version
0.5.0-alpha
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Kubernetes with Helm
Additional Context
It looks like this issue has been introduced with #359, which basically creates a new counter for each and every request.
The text was updated successfully, but these errors were encountered: