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 and unstable CPU / Mem usage for the archive on bullseye #39

Open
jooola opened this issue Feb 9, 2022 · 2 comments
Open

High and unstable CPU / Mem usage for the archive on bullseye #39

jooola opened this issue Feb 9, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@jooola
Copy link
Owner

jooola commented Feb 9, 2022

The CPU and memory usage of the archiver is unstable and sometimes uses the entire virtual machine resources. This happens on bullseye, while it wasn't an issue on buster.

I previously added a way to set the -re flag and -copy flag to prevent the archiver to eat too much resources, but it seems we have another issue here.

@jooola jooola added the bug Something isn't working label Feb 9, 2022
@jooola
Copy link
Owner Author

jooola commented Feb 9, 2022

image

Earhorn has process metrics exported using prometheus, I'll try to put them in meaningful charts to maybe find some more clues.

@jooola
Copy link
Owner Author

jooola commented Feb 14, 2022

I've experimented quickly with other builds of ffmpeg and it seems the ffmpeg version packaged by debian is the source of this bug. Still needs more investigation.

As workaround I'll try running with another build of ffmpeg in production and see how it goes.

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

1 participant