четверг, 1 апреля 2021 г. в 16:02:15 UTC+3, Barry: > > On 1 Apr 2021, at 13:46, Marco Ippolito <marol...@gmail.com> wrote: > > > > > >> > >>>> What if you increase the machine's (operating system's) swap space? Does > >>>> that take care of the problem in practice? > >>> > >>> I can`t do that because it will affect other containers running on this > >>> host. > >>> In my opinion it may significantly reduce their performance. > >> > >> Assuming this a modern linux then you should have control groups that > >> allow > >> you to set limits on memory and swap for each container. > >> > >> Are you running with systemd? > > > > If their problem is that their memory goes from `<low>` to `<high>` and > > then > > back down to `<mid>` rather than `<low>`, how could `cgroups` have helped > > in > > that case? > > > > I suspect the high watermark of `<high>` needs to be reachable still and, > > secondly, that a forceful constraint whilst running would crash the > > container? > > > > How else could one approach it? > > > I was responding to the assertion that adding swap to the system would impact > other containers. > The solution I have used is to set service/container resource limits to > ensure they work as expected. > > I was not suggestion this a fix for the memory leak.
I think it's good advice anyway. Thanks! -- https://mail.python.org/mailman/listinfo/python-list
