Reschedule Log screen

[Tim Norton]

Fred

just noticed something in the log window it might be just cosmetic but...

From log window
est_ratio_cpu_min: 0.500000
est_ratio_cpu_max: 2.500000
est_ratio_gpu_min: 0.500000
est_ratio_cpu_max: 4.000000

from config file
<est_ratio_cpu_min>0.5</est_ratio_cpu_min>
<est_ratio_cpu_max>2.5</est_ratio_cpu_max>
<est_ratio_gpu_min>0.5</est_ratio_gpu_min>
<est_ratio_gpu_max>4.0</est_ratio_gpu_max>

as you can see the last line of the log window is incorrectly showing cpu rather than gpu

[Tim Norton]

Sorry should have said this is v1.6

[fred]

Sorry should have said this is v1.6

Thanks, corrected.

[Darth_Caedus]

---------- Seti override begin
DCF low: 0.900000
DCF max: 1.100000
Vlar: 0.130000
Vhar: 1.127000
est_ratio_cpu_min: 0.200000
est_ratio_cpu_max: 4.600000
est_ratio_gpu_min: 2.600000
est_ratio_cpu_max: 2.900000
I change that, like today standard server DCF and like factors see under<
---------- Seti override end
---------- Debug begin
log_all_tasks = 1
rsc_fpops = 1
---------- Debug end
07 August 2010 - 14:18:00 BoincRescheduler V: 1.6


07 August 2010 - 14:18:02 Application setiathome_enhanced found, Version: 603
07 August 2010 - 14:18:02 Application setiathome_enhanced found, Version: 609 , Plan class: cuda23
07 August 2010 - 14:18:02 Found: CPU: 6, VLAR: 4, VHAR: 0
07 August 2010 - 14:18:02 Found: GPU: 239, VLAR: 0, VHAR: 27
07 August 2010 - 14:18:02 Average: Ratio Cpu: 1.698179, count: 6, invalid 0 ,Average: Ratio Gpu: 2.749627, count: 239, invalid 0
07 August 2010 - 14:18:02 Ratio CPU: min: 0.214195 max: 4.585872 - Ratio Gpu: min: 2.606116 max 2.813878
07 August 2010 - 14:18:02 No rescheduling needed

What say it about my system ?
Have anyone tips for optimise ?

thanks for help
greetings

[fred]

What say it about my system ?
Have anyone tips for optimise ?

thanks for help
greetings

As I'm not sure if the correction system, that is running is really working as it should.

A higher ratio moves the DCF up. But any DCF value is ok as long as it's steady.
As I've seen on other computers, is that the ratio on the CPU. Some WU have a very low and others a very high ratio.
This will swing the DCF around and will vary the time estimates.

We can't do much except setting the -177 check to make sure there aren't any timeout errors.
You are already setting a min and max value. For now waiting is the best option.