One thing not yet explicitly mentioned on this thread: the recommendation is one *concern* per container, not necessarily one OS process. As Hynek said, that a single-worker gunicorn container is actually two processes is an uninteresting implementation detail. The number of OS processes is unrelated to achieving the goals of one concern per container.
— Theron > On Sep 18, 2019, at 8:39 AM, Mikko Ohtamaa <[email protected]> wrote: > > > > >> - I also do 1 proc/Docker image, I would recommend to have a look on >> https://pythonspeed.com/docker/ for various things to keep in mind if you >> haven’t seen it already. > > I am very familiar with the trade offs and tuning of process vs. threads. > Now, when this conversation is going on, would someone comment trade offs > between container vs. process? Is it radically more memory/CPU sensitive? Are > things like logging and external service API access harder to arrange? What > are the trade offs and benefits? > > Br, > Mikko > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pylons-discuss/CAK8RCUum%2BvHLxWMDqHiiLvHZxq%2BrQu-jAgL7AN6pW7%3DgbQq%2BHw%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/0BDC7730-3BD4-4022-B9B0-8C3C0E73C0EE%40luhn.com.
