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

probably resources leak when LOG_LEVEL=trace #1

Open
alexeyshindig opened this issue Oct 28, 2021 · 1 comment
Open

probably resources leak when LOG_LEVEL=trace #1

alexeyshindig opened this issue Oct 28, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@alexeyshindig
Copy link

Hi!

I've just faced up with significant resources consumption running turnserver-healthcheck as docker-container with LOG_LEVEL=trace
Pay attention to the "File Descriptors used" & CPU usage metrics, as well as memory:
image

1st peak was produced by sending ~20 requests once per minute
2nd and 3rd ~5 requests once per minute.
The resource consumption reset when the container was restarted.
After disabling LOG_LEVEL=trace I can't see any troubles running ~30 checks per minute for more than 1.5 hrs

Host environment: t3.medium instance in AWS (2CPU, 4G RAM), Amazon Linux 2

Have a nice day!

@Bastian Bastian added the bug Something isn't working label Nov 2, 2021
@Bastian
Copy link
Member

Bastian commented Nov 2, 2021

Hello,

Thank you for reporting! I will take a look at the issue.

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

2 participants