@hynek you are not using 1 process per container. You are using gunicorn or
haproxy instead of the container and those talk to python?

On Tue, Sep 17, 2019 at 12:25 PM Jonathan Vanasco <[email protected]>
wrote:

>
>
> On Monday, September 16, 2019 at 8:37:17 PM UTC-4, hynek wrote:
>
>
>> - I don’t know whether it’s me, my Python DB driver (sqlanydb 😞), or the
>> underlying libs: there’s stuff leaking all the time so I wouldn’t use a
>> WSGI container that doesn’t do worker recycling after a configurable amount
>> of requests served. Otherwise you get best case uncontrolled recycling via
>> crash and worst case deadlocks.
>>
>
> this is actually the main reason why I adopted uwsgi. a hook loads most of
> the Python we need into the shared memory before the fork, and then workers
> are recycled to our specs.
>
> how do you avoid leaks / leak-like process growth in the threaded gunicorn
> solution you adopted?
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pylons-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pylons-discuss/fkD20M94XBM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/5df47be5-5f1a-40cc-870b-9e5132925434%40googlegroups.com
> <https://groups.google.com/d/msgid/pylons-discuss/5df47be5-5f1a-40cc-870b-9e5132925434%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Alexander D. Mills
New cell phone # (415)730-1805
[email protected]

   - www.linkedin.com/pub/alexander-mills/b/7a5/418/

-- 
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/CA%2BKyZp6vUjjGA-Bq6Kt6OO8WK5EjHDKq12XyyHn9PfWBsqktCA%40mail.gmail.com.

Reply via email to