5.8.8 client and DCF
3 Feb 2007 1:05:32 UTC
Topic 192378
(moderation:
My DCF is growing steadily with each WU crunched until the ETA shown in boincmgr has no basic with reality.
I do a pair of WU's in 2:10, which for my system needs a DCF of .45. Coming home from work today I saw the ETAs at 3:45, while the completed nonuploaded WUs were sitting at 2hrs. I stoped boincmgr and edited the DCF down from .7 to .45 to get the ETAs back in line, but they've already crept back to 2:45 while the actual WUS are still finishing in 2:10.
5.8.8 client and DCF
)
Please take a look at this thread over on the BOINC message boards. This behaviour has been around for virtually all of the 5.8.x series and has been reported several weeks ago. The above link contains a response from David Anderson with some brief information on the cause of the bug. There is also a comment indicating that it should have been fixed in 5.8.7.
If it's NOT fixed in 5.8.8, I would expect a 5.8.9 to come along RSN :).
Cheers,
Gary.
We hope it's fixed in
)
We hope it's fixed in 5.8.9
That version will first be tested by the alpha testers though. Luckily I am one of them and I will thoroughly test this. ;-)
I'm seeing the same problem
)
I'm seeing the same problem in the Mac version of BOINC 5.8.8. My RDC factor has no basis on reality, as my MacBook crunches work units in 3 hours or less but the estimated crunch times are now over 5 hours. How does one correct the RDC factor to bring it back to reality?
Thanks.
RE: How does one correct
)
In short, you can't. You can see its current value in your state file (client_state.xml) and from the figures you quote, your current (but incorrect) value would be around 0.6. The correct value should be around (0.6)^2 ie, 0.36, and if you were to stop BOINC and edit the state file to change the actual number you see to its square you would temporarily get things to look the way they should. However, because of the bug in the 5.8.x series so far, the value you set will be progressively moved back to the one you see now, ie around 0.6.
Your only real option is to grab 5.8.9 as soon as it comes out and hope that the bug has been fixed there.
Cheers,
Gary.
IF you only run a single
)
IF you only run a single project, or have similar DCFs on all, you can change the Connect every N days setting to provide the ammount of work reserve you want to carry.
RE: IF you only run a
)
Absolutely, but you will need to be paying attention if you upgrade in future to a "bug-fixed" version of BOINC :).
Cheers,
Gary.
True, but since you have to
)
True, but since you have to actively make the change in the first place it shouldn't be a major issue, the casual user won't do it.
In my personal case, I generally toggle between 3 and 5 days whenever I'm going away for a weekend, or my ISP has scheduled maintaince coming. I haven't had any problems with the later yet but am playing it safe.
OTOH I figured out that a major bandwidth upgrade was coming a few months before the official announcment because my large xfers were running significantly faster than normal. I suppose they wanted to be sure they could handle the planned increase before making an anouncment to the users.
The DCF fix is in the 5.8.9
)
The DCF fix is in the 5.8.9 client. It only missed being in 5.8.8 by a few hours.
BOINC WIKI
BOINCing since 2002/12/8
Any idea on when 589 will be
)
Any idea on when 589 will be released?
It's not even out for testing
)
It's not even out for testing yet. Expect about a week of testing before it is released unless a serious problem is found in the current version.
BOINC WIKI
BOINCing since 2002/12/8