Hi Daniel,
For each node Ducc sums RSS for all "system" user processes and excludes
that from Ducc usable memory on the node. System users are defined by a
ducc.properties setting with default value:
ducc.agent.node.metrics.sys.gid.max = 500
Ducc's simulation mode is intended for creating a scaled out cluster of
fake nodes for testing purposes.
The only mechanism available for reserving additional memory is to have
Ducc run some dummy process that stays up forever. This could be a Ducc
service that is automatically started when Ducc starts. This could get
complicated for a heterogeneous set of machines and/or Ducc classes.
Can you be more precise of what features you are looking for limiting
resource use of Ducc machines?
Thanks,
Eddie
On Mon, Oct 31, 2016 at 10:03 AM, Daniel Baumartz <
bauma...@stud.uni-frankfurt.de> wrote:
> Hi,
>
> I am trying to set up nodes for Ducc that should not use all the memory on
> the machine. I tried to limit the memory with cgroups, but it seems Ducc is
> getting the memory info from /proc/meminfo which ignores the cgroups
> settings.
>
> Did I miss an option to specify the max usable memory? Could I safely use
> "ducc.agent.node.metrics.fake.memory.size" from the simulation settings?
> Or is there a better way to do this?
>
> Thanks,
> Daniel
>
>
