make the dagbegins request less memory
Not sure what a dagbegin is or why it's there since it literally does NOTHING!!!
Anyway, don't require 2GB for it at least. Request 100Kbytes or something so it runs right away and gets out of the way if you can't get rid of it compeletely.
-bash-4.1$ condor_q -nobatch -constraint 'owner == "kotwal"' -af cmd requestmemory
They can sit for a long period of time for experiments with a low quota sometimes holding up jobs that are requesting much less memory which would also run in a busy batch system if this dagbegin wasn't stuck waiting for 2GB of memory.
#1 Updated by Dennis Box 6 months ago
- Status changed from New to Feedback
- Assignee changed from Dennis Box to Shreyas Bhat
- Target version set to v1.2.9
See jobsub branch 21440
configurable request_memory parameter for 'dag_begin dag_end sam_begin sam_end' files.
Default value is 100kb. Can be changed in jobsub.ini in [default] section, example
dag_start_memory = 33kb
This seems to have broken things. Looks like 4MB is a minimum.
HoldReason = "Error from firstname.lastname@example.org: Error response from daemon: Minimum memory limit allowed is 4MB "
The default in the code should be set to probably 100MB or something. Does everyone submitting a dag have a dagstart or is this just a CDF thing? A requirement of 100MB is very small but should handle I would think most shell scripts unless maybe people do large sam commands in them. If other people have dag starts do they actually put whatever they want in the dag start or does jobsub always create a dag start?
I don't want to role this out and have a break a bunch of things because the limit is too small.