The server should be now ignoring dcf for the time being.
I will reuse it in a couple of weeks when things are stabilized.
Let me know if the situation improves.

gdf

OK

It has started to drop from the 100.

Last check shows DCF at 99.011805. I will leave my host 6133 untouched, so as it can be monitored to see if it corrects back to near 1. Although it will be slow as it takes 16 hours per task. I will check again before I leave on vacation, in about 5 days, then it has 10 days to run untouched.

Join team USA

I still do not get another task when one finishes, only way is to suspend other running projects which will force the schedule to request work, then I can resume the other projects. I assume once the DCF drops lower this behavior will stop.

The DCF is again goof up on my PC. After this WU 161943 the next WU 162890 have again to run with a destroyed DCF of 60.830372 and a estimated runtime of over 80 hours. I'm really one of the hardest while testing software, but the actual situation is annoying. Looks like it's the wrong way to play with the DCF to control the behavior of he GPU work priority.
____________

The DCF is again goof up on my PC.

My DCF on this host has jumped back up to 100.

I reset several Box's this morning, when the new Wu's Downloaded 2 of them showed 22:00:00 Hours to completion (which is still about 4 times what it should be) & 2 showed 279:00:00 Hours to completion. I'm about 1/2 thru the first Wu & when I checked my DCF in the client_state.xml file it showed only 1.000000 for a DCF Value.

So I take it the DCF Value in the .xml file won't change until after the first Wu is finished, also if the Value was reset to 1.000000 why do 2 of the Wu's still show 279 Hours to completion when they Downloaded ... ???

hmm - I have been seeing this message quote:
"Message from server:(wont finish in time) BOINC runs 97.4% of time, computation enabled 100.0% of that" and cant get any WU's.

I went and reset the project and immediately gpugrid downloaded two tasks. Time to complete is just under 14 hours, about right.

Not sure that is going on and that error message does not make a lot of sense. I always have computation enabled 100% and BOINC runs all the time.

hmm - I have been seeing this message quote:
"Message from server:(wont finish in time) BOINC runs 97.4% of time, computation enabled 100.0% of that" and cant get any WU's.

I went and reset the project and immediately gpugrid downloaded two tasks. Time to complete is just under 14 hours, about right.

Not sure that is going on and that error message does not make a lot of sense. I always have computation enabled 100% and BOINC runs all the time.

.......... I'm seeing some improvement - last couple of WUs came down with a 30hour ETA.
GDF - it would be nice if you could summarise the project's current position & advice to crunchers. In one place it would be good to have your thoughts on downgrading the client - or not, manually adjusting the DCF, hanging in there....etc.

P.

.......... I'm seeing some improvement - last couple of WUs came down with a 30hour ETA.
GDF - it would be nice if you could summarise the project's current position & advice to crunchers. In one place it would be good to have your thoughts on downgrading the client - or not, manually adjusting the DCF, hanging in there....etc.

P.

I'm seeing some improvement - last couple of WUs came down with a 30hour ETA. - Burdett

It doesn't seem to matter if you Downgrade the Client which I did on all my Box's last night, or if you manually adjust the DCF, or if you Re-Set the project, the Wu's still come with hap-hazardly To Completion Times. - Poorboy

about time for a new highscore-thread?

latest one started with 1190 hours on an 260..

next one: 18300 hours - rising like mad..

My latest completed WU was back to the shorter ones: Last WU.

2435 credit vs. 3232 credit

Is there any correlation between this issue with high estimated times / high priority tasks and the smaller WU's? Once it reverted back to the "3232" WU's 2 days ago, my rig appear to stabilize and work correctly. That is until it started process the "2435" WU's again.

... I'm back to 'work not available for your type of computer' message - followed by the 24hour 'sod off' back off.
As it now appears we have to manage GPUGrid manually - could we remove (or double) the 1 WU per CPU limit - I can get through 8 WUs in 24 hours or so on one of my hosts ... if I could load up, the 24hours backoff could pass without idle time. Or just reduce the 24 backoff to something more useful - 6 hours?



P.

Which workunit name?

gdf

OK, Mine dropped again from 100 to 'Task duration correction factor 91.193244'

This will be my last post. I have some more last minute preparaions for vacation tonight, then I'm off tomorrow for 12 days. MErry Christmas to all, see you all later, much later.

... and there must still be an error in the workunits, that's messed up the DCF. After reporting this workunit 170459 my DCF goes up to 7.478452 and the estimated time of the next WU jumps from the regular 6:28 up to over 60 hours, the task fall in high prio mode and blocks the load of another workunit.
____________

... and there must still be an error in the workunits, that's messed up the DCF. After reporting this workunit 170459 my DCF goes up to 7.478452 and the estimated time of the next WU jumps from the regular 6:28 up to over 60 hours, the task fall in high prio mode and blocks the load of another workunit.

Try to restart project. `Full restart` with detaching and deleting all files which will be not removed after detaching.