045.000: Run analysis summary. Of 12 machines,
~ 1 are rejected by your job's requirements
~ 6 reject your job because of their own requirements
~ 0 match, but are serving users with a better priority in the pool
~ 4 match, match, but reject the job for unknown reasons
| 300 second delays can occur if the new job started while condor was
| within a 20 seconds frame of the negotiation cycle. you can start the
| job by using condor_reschedule.
| you can reduce the time by lowering the NEGOTIATOR_INTERVAL value, but
| the 20 seconds timeframe is fixed, so for a 60 second interval you have
| a 33% chance that your job must wait up to a minute.
That's clear to me, I did not expect the queued jobs to be executed
within a few seconds, but (recaling my first mail) it was unclear to me,
why sometimes (not allways) jobs don't get executed for 10-30 minutes
while "condor_status" lists a lot of machines (all of them Windows in my
case) as Unclaimed/Idle during that period.