Justus Winter writes:
> But currently Mailman3 does fork+exec, so it doesn't get to share
> the parent's pages. I experimented with fork-and-dont-exec [0],
> but the results were underwhelming, because reference counting can
> cause pages to diverge. Surprisingly, gc.freeze didn't seem to
Hi :)
"Stephen J. Turnbull" writes:
> Hi Justus!
>
> > Besides cleanups and bugfixes, there are three things I'd like to
> > do:
> >
> > - Improve Mailman to better scale down to small installations
>
> Not sure what you can really do about that without rearchitecting.
> The full suite
"Stephen J. Turnbull" writes:
> Дилян Палаузов writes:
>
> > Do you know by accident, if the runner processes use identical
> > memory, and by
> > calling https://man7.org/linux/man-pages/man2/madvise.2.html the
> > kernel can somehow detect these identical memory and then use a
> >
Дилян Палаузов writes:
> Do you know by accident, if the runner processes use identical
> memory, and by
> calling https://man7.org/linux/man-pages/man2/madvise.2.html the
> kernel can somehow detect these identical memory and then use a
> single instance for all identical regions of
Hello Justus,
I find it very good that you are trying to reduce the memory consumption of
mailman 3. I cannot help in doing this. I hope you find some way to reduce
the memory.
Do you know by accident, if the runner processes use identical memory, and by
calling
