On Wed, Nov 18, 2015 at 7:51 PM, Itamar Reis Peixoto
wrote:
> try systemd-nspawn and use it instead of virtualizing, will save you some
> bits of memory.
Interesting.. Not an option for us currently but perhaps as an
alternative to Docker it will come in handy.
Thanks for the feedback.
Kwan
___
Warren:
Thanks for the good info and link.
On Wed, Nov 18, 2015 at 4:41 PM, Warren Young wrote:
> On Nov 18, 2015, at 1:20 PM, Kwan Lowe wrote:
>>
>> Because of caching, from VMWare's perspective, all Linux memory is
>> being "used”.
>
> Nope. VMware’s memory ballooning feature purposely kee
On Nov 18, 2015, at 5:51 PM, Itamar Reis Peixoto
wrote:
>
> On 2015-11-18 19:41, Warren Young wrote:
>> On Nov 18, 2015, at 1:20 PM, Kwan Lowe wrote:
>
> try systemd-nspawn and use it instead of virtualizing, will save you some
> bits of memory.
That’s fine if you’re after the isolation feat
On 2015-11-18 19:41, Warren Young wrote:
On Nov 18, 2015, at 1:20 PM, Kwan Lowe wrote:
try systemd-nspawn and use it instead of virtualizing, will save you
some bits of memory.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mai
Warren Young wrote:
> On Nov 18, 2015, at 1:20 PM, Kwan Lowe wrote:
>>
>> Because of caching, from VMWare's perspective, all Linux memory is
>> being "used”.
>
> Nope. VMware’s memory ballooning feature purposely keeps some of the
> guest’s RAM locked away from the kernel. This is where RAM come
On Nov 18, 2015, at 1:20 PM, Kwan Lowe wrote:
>
> Because of caching, from VMWare's perspective, all Linux memory is
> being "used”.
Nope. VMware’s memory ballooning feature purposely keeps some of the guest’s
RAM locked away from the kernel. This is where RAM comes from when another
guest n
Hello everyone,
Excuse the title. I'm trying to do something very specific that goes
against some common assumptions.
I am aware of how Linux uses available memory to cache. This, in
almost all cases, is desirable. I've spent years explaining to users
how to properly read the free output.
I'm no
7 matches
Mail list logo
