> Am 29.02.2016 um 23:27 schrieb Ben Daniel Pere :
>
> It's the other way round. The load used in the load_formula is already
> adjusted. You adjust individual values, not the result of any computation
> already made with them.
>
> The computed load_formula will then be used to sort the machin
>
> It's the other way round. The load used in the load_formula is already
> adjusted. You adjust individual values, not the result of any computation
> already made with them.
>
> The computed load_formula will then be used to sort the machines.
>
Oh load formula is just for machines priority? so
> Am 28.02.2016 um 21:51 schrieb Ben Daniel Pere :
>
> Each job starting on a machine will contribute 1 to the adjustment which will
> decay over time to 0, in your case in 7:30 minutes. The 38.23 is the sum of
> all these adjustments of all jobs starting in the last 7:30 while each job
> will
>
> Each job starting on a machine will contribute 1 to the adjustment which
> will decay over time to 0, in your case in 7:30 minutes. The 38.23 is the
> sum of all these adjustments of all jobs starting in the last 7:30 while
> each job will have it's own individual contribution to this sum. If n
Hi,
Am 28.02.2016 um 17:03 schrieb Ben Daniel Pere:
> I'm looking into several cases where jobs don't enter our queues even though
> the load is lower than the threshold and I noticed there's a different
> calculation there I can't figure..
>
> Turning on logging, I see the following on qstat
I'm looking into several cases where jobs don't enter our queues even
though the load is lower than the threshold and I noticed there's a
different calculation there I can't figure..
Turning on logging, I see the following on qstat -j on a job that should
enter but isn't:
queue instance "al...@n38
