Since a few days my machine calculate WUProp@Home work units...
The estimated time of the work units was correct a long time (~ 3 hours).
Then I made a reboot of my machine and then the estimated times are too high (~ 3 days).
I didn't looked to the Duration Correction Factor before, but now it's ~ 28.
Normally it should be ~ 1.
Is this a known problem?
____________
/ 
Reply
Quote
Then I made a reboot of my machine and then the estimated times are too high (~ 3 days).
You mean, after 10 WUs were validated and the "server side DCF" kicked in? Yeah, had that on all my machines. Not nice, but with 1 task/machine limit it actually doesn't matter.
I didn't looked to the Duration Correction Factor before, but now it's ~ 28.
Normally it should be ~ 1.
You have a DCF for WUProp@Home? On all my machines the entire scheduling part (to which the DCF belongs) of project's properties is missing... all I have is "General" and "Credit".
____________
.
/ Reply
Quote
OK, there is a DCF in the client_state.xml. It's adjusting itself slowly to the new estimates send by the server. The first WU had IIRC an estimated runtime of just few minutes, so that's where the high DCF comes from.
____________
.
/ Reply
Quote