On Wednesday, September 18, 2019 at 1:34:57 AM UTC-4, hynek wrote:
>
>
> This means "recycle after 4096 +/- 128 requests” (The jitter is so they
> don’t recycle all at once; although it’s unlikely to happen at the same
> time over the whole cluster. The option is more useful when you have more
- 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 som
On Monday, September 16, 2019 at 8:37:17 PM UTC-4, hynek wrote:
- HAProxy kicks nginx’s and Apache’s behinds in almost every regard. This
> is my hill. I like my hill. I will retire on this hill.
>
I really like HAProxy and Varnish. They were both keystones to some high
traffic sites I worke
> - 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
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 unr
