Hello Experts,Â
We found that RecentDaemonCoreDutyCycle is a crucial parameter to decide whether sched jobs will be considered for match making or not. We noticed other Recent* parameters which are helpful to gather more information about sched. But the results of these parameters does not match with numbers of condor_q. I understand these parameter change in range from 0 to 20m but we never see the number of jobs submitted in the last 20mins more than 3-4k and the number we see is 6k, similarly for started and exited.Â
  [
    Autoclusters = 16;
    RecentStatsLifetime = 1200;
    Name = "
test.example.com";
    RecentDaemonCoreDutyCycle = 3.490321919877746E-01;
    RecentJobsExited = 9820;
    RecentJobsKilled = 2;
    RecentJobsStarted = 10078;
    RecentJobsSubmitted = 6049
  ]
Is't necessary to keep STATISTICS_WINDOW_SECONDS more than STATISTICS_WINDOW_QUANTUM. If we are changing the default of 20m to somewhat like 5m to get more granular metrics from sched. Is't increasing the memory needs of sched?
test:~# condor_config_val STATISTICS_WINDOW_SECONDS STATISTICS_WINDOW_QUANTUM
1200
240
What's the logic to increase RecentDaemonCoreDutyCycle? Based on the number of jobs in the queue or any other parameter also?Â
Thanks & Regards,
Vikrant Aggarwal