Yes, exactly.
Best Regards,
Christopher Wong
From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Sent: Thursday, March 10, 2022 2:52:38 PM
To: Christopher Wong
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: PrivateNetwork=yes is memory costly
Sent: Thursday, March 10, 2022 2:52:38 PM
To: Christopher Wong
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: PrivateNetwork=yes is memory costly
On Do, 10.03.22 11:50, Christopher Wong (Christopher.Wong@xxxxxxxx) wrote:
> Hi Lennart,
>
>
> It is definitely a functionality we want to use. However, the memory came as an unexpected side effect. Since we are not only enabling this for one single service, instead we are applying it globally for all services.
>
> Now due to this huge memory consumption we are trying to put
> everything into the same namespace using
> JoinsNamespaceOf=<some-service>. It seems to consume less memory.
This means they will still be isolated from the network, but no longer
from each other.
Lennart
--
Lennart Poettering, Berlin
> Hi Lennart,
>
>
> It is definitely a functionality we want to use. However, the memory came as an unexpected side effect. Since we are not only enabling this for one single service, instead we are applying it globally for all services.
>
> Now due to this huge memory consumption we are trying to put
> everything into the same namespace using
> JoinsNamespaceOf=<some-service>. It seems to consume less memory.
This means they will still be isolated from the network, but no longer
from each other.
Lennart
--
Lennart Poettering, Berlin
