H,
> Ondrej
>
> Get Outlook for Android <https://aka.ms/ghei36>
> From: berg...@merctech.com
> Sent: Friday, August 7, 2020 7:11:11 PM
> To: Ondrej Valousek
> Cc: users@gridengine.org ; Trimboli, David
>
> Subject: Re: [gridengine users] m_mem_free and cgroups
>
> I'm trying to limit memory usage
We use UGE and we/I have addressed high memory usage/reservation as follows:
- we have different types of queues, a matrix of memory limits and time
limits (the elapsed time limit is always 2x cpu limit on our system), you
do this via the queue def
d
Subject: Re: [gridengine users] m_mem_free and cgroups
In the message dated: Fri, 07 Aug 2020 16:24:16 -,
The pithy ruminations from Ondrej Valousek on
[Re: [gridengine users] m_mem_free and cgroups] were:
=> Short answer: Use a different tool than stress Long answer: linux kernel
=>
In the message dated: Fri, 07 Aug 2020 16:24:16 -,
The pithy ruminations from Ondrej Valousek on
[Re: [gridengine users] m_mem_free and cgroups] were:
=> Short answer: Use a different tool than stress Long answer: linux kernel
=> is too clever for tests like stress because allocating a
Okay, what would make a good test of this, then? And is my configuration
correct?
From: Ondrej Valousek
Sent: Friday, August 07, 2020 12:24 PM
To: users@gridengine.org; Trimboli, David
Subject: Re: m_mem_free and cgroups
Short answer: Use a different tool than stress
Long answer: linux kernel
Short answer: Use a different tool than stress
Long answer: linux kernel is too clever for tests like stress because
allocating a memory is one thing (which is taken only like "alright, i'll see
what i can do, here is the pointer") but actually _using_ that memory is
something completely differe
