Open TomTinking opened 8 months ago
CPU limitation can be done by Docker during creation of the container. So I don't see the need to add/implement something else to the container itself.
Agree but was surprised how much it hogged resources on my NAS.. I have many containers (sonarr etc).. and they have never hogged so much resource before..
Yes, MakeMKV is very I/O extensive :)
So what were your expectations by creating this issue ?
Maybe just a suggestion in the docs.. as yeah it was big on the I and O.
Maybe just a suggestion in the docs.. as yeah it was big on the I and O.
Telling people to handle basic docker resource management seems an odd ask of a repo
Idea
I suggest the container using at most 2 CPU threads. I had this set to unlimited and it used all resources on the NAS and it became unstable. I set it to 2 and this made it more stable and speed was absolutely fine.