Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] ep custom configuration
- Date: Fri, 25 Apr 2025 15:29:00 +0200
- From: Antonio Falabella <antonio.falabella@xxxxxxx>
- Subject: Re: [HTCondor-users] ep custom configuration
Hi Thomas,
the DAQ jobs will not go through condor, this is why condor should have
a way to identify the machine as "idle" as it is for boinc opportunist
computing.
Thanks
Antonio
On 25/04/25 14:42, Thomas Hartmann wrote:
Hi Antonio,
an ad hoc idea might be to define a custom resource, i.e., with the
concurrency_limit as consumable resource (and set it to zero when the
DAQ ramps up on your farm).
If it would be sufficient to have Condor jobs still on your DAQ farm
but with a fraction of the resources, a drop-in unit with only a
fraction of the overall CPU quota for the whole Condor unit might be
also an option (if DAQ/jobs are just CPU limited...)
Cheers,
 Thomas