-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Memory problem ? #86
Comments
Can you double check that the issue goes away when downgrading the prometheus crate to v0.12.0? How did you do that? |
The weird thing is that one device works with prometheus v0.12.0 and another does not (release 0.9.1), but both devices work well with encrypted-dns release 0.3.23 and arm32v7/ubuntu:22.04 Build dnscrypt-server-docker, FROM arm32v7/ubuntu:22.04 |
I have also tried prometheus v0.13.1, but there are also issues. |
Does it still happen if you don't enable the |
I have to try. |
Ok, so at least we know that this is unrelated to Prometheus. In case this is not in a dependency, would you be able to pinpoint a specific commit that introduced this? |
Version 0.3.23 works. Version 0.9.0 does not work. So there must be something between these versions. Will probably have to test more to find the specific commit that introduced this. |
I think this problem is due to jemallocator. See what was mentioned earlier. I have tried with tikv-jemallocator. Compiled fine and without memory problem, but unfortunately no response from encrypted-dns. Only gets TIMEOUT on server in dnscrypt proxy. |
So, like way too many Rust crates, jemalloc is abandoned, and the maintained fork doesn't work on ARM? Great :( As an experiment, 748b944 replaces |
The app doesn't seem to compile at all on armv7 :(
|
tikv/rust-prometheus#442 |
After removing prometheus' |
Update. |
I have had memory problems in dnscrypt server-docker images.
Memory usage is growing rapidly.
Come across this:
tikv/rust-prometheus#424
Could prometheus v0.13.0 be the problem?
Compiled encrypted-dns with prometheus v0.12.0 and it looks like memory problem is gone.
This was done on a singleboard computer arm32v7 with 2Gbyte of LPDDR3 RAM.
The text was updated successfully, but these errors were encountered: