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
To prevent this kind of situation from recurring, we could consider limiting usage by docker Memory, CPUs, and GPUs.
I'd like to know the best practices on this subject (which parameters to play with ... hard or soft limits for memory..... if the rpi has 4 CPUs, is relevant to setup a limit to 3.8 .. etc ), which limitations to implement, and whether there are any constraints to implementing this type of docker limitation.
I would tend to think that we want to minimize the limits imposed on the docker service, but make sure we avoid a complete host crash
Thank you in advance for your suggestions.
The text was updated successfully, but these errors were encountered:
According to docker documentation :
and this is how pyro-engine actually works.
However, we have recently encounter issues, rpi crash, probably due to a due to excessive use of multiprocessing and it has needed manual reboot.
pyro-engine/pyroengine/core.py
Line 4 in feb54de
To prevent this kind of situation from recurring, we could consider limiting usage by docker Memory, CPUs, and GPUs.
I'd like to know the best practices on this subject (which parameters to play with ... hard or soft limits for memory..... if the rpi has 4 CPUs, is relevant to setup a limit to 3.8 .. etc ), which limitations to implement, and whether there are any constraints to implementing this type of docker limitation.
I would tend to think that we want to minimize the limits imposed on the docker service, but make sure we avoid a complete host crash
Thank you in advance for your suggestions.
The text was updated successfully, but these errors were encountered: