Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Mikolaj Kowalik
Mikolaj KowalikReporter
Mikolaj Kowalik
Mikolaj KowalikLabels
Reviewers
Michelle Gower
RubinTeam
Data Facility
Components
Checklist
Checklist
Created April 29, 2024 at 6:28 PM
Updated June 10, 2024 at 8:35 PM
Resolved June 10, 2024 at 8:35 PM
For automatic memory scaling to work in ctrl_bps_htcondor,
memoryLimit
must be set. Normally, it should reflect the actual limitations of the computational resource (e.g. the largest memory value among available HTCondor execution points). However, at SLAC there’s no native HTCodnor execution points as they are created dynamically using glideins governed byallocateNodes.py
. AsallocateNodes.py --auto
is able to adjust memory requirements for the glideins based on the memory requirements of the jobs in the HTCondor job queue in order to enable using automatic memory scaling it should be sufficient to provide a default value formemoryLimit
. The goal is to include a YAML file that will provide a default value for this parameter in ctrl_bps_htcondor as well as making any changes so it can be set as any other BPS parameter (in decreasing order of priority):as a command line option,
in the user’s BPS config,
in plugin’s defaults,
in BPS defaults.