Forum > GPU crunching
BOINC 6.10.58/server estimates - still wrong?
Raistmer:
After doing some amount of AP tasks my GPU fetched MB tasks again. And all were marked ~22-23 min of estimated time.
Even VLAR ones.
Definitely my GPU takes much longer to compute them. To this point it finished much more than 10 MB tasks so server estimates should be stable.
So, AP work still affects on MB estimates?
Or smth scewed again on server side?
Very probably I get -177 errors on all or most of just downloaded tasks... :(
Josef W. Segur:
--- Quote from: Raistmer on 20 Feb 2011, 05:00:44 am ---After doing some amount of AP tasks my GPU fetched MB tasks again. And all were marked ~22-23 min of estimated time.
Even VLAR ones.
Definitely my GPU takes much longer to compute them. To this point it finished much more than 10 MB tasks so server estimates should be stable.
So, AP work still affects on MB estimates?
Or smth scewed again on server side?
Very probably I get -177 errors on all or most of just downloaded tasks... :(
--- End quote ---
Duration Correction Factor in the core client applies to (and reacts to) all tasks for the project. If it is 1 then the elapsed time limit is 10x the estimate. But if DCF is 10 the limit is the same as the estimate, or if DCF is 0.1 the limit is 100x the estimate.
Certainly it's also possible there's a server side problem, I noticed a couple of NC forum posts about -177 errors but without enough detail.
Joe
skildude:
I noticed that my ATI WU's were estimated for 7 hours yet the CPU WU's were all around 2 hours. the 2 hour WU's are about right so what gives with the ati ones
Raistmer:
--- Quote from: Josef W. Segur on 20 Feb 2011, 10:51:43 pm ---
--- Quote from: Raistmer on 20 Feb 2011, 05:00:44 am ---After doing some amount of AP tasks my GPU fetched MB tasks again. And all were marked ~22-23 min of estimated time.
Even VLAR ones.
Definitely my GPU takes much longer to compute them. To this point it finished much more than 10 MB tasks so server estimates should be stable.
So, AP work still affects on MB estimates?
Or smth scewed again on server side?
Very probably I get -177 errors on all or most of just downloaded tasks... :(
--- End quote ---
Duration Correction Factor in the core client applies to (and reacts to) all tasks for the project. If it is 1 then the elapsed time limit is 10x the estimate. But if DCF is 10 the limit is the same as the estimate, or if DCF is 0.1 the limit is 100x the estimate.
Certainly it's also possible there's a server side problem, I noticed a couple of NC forum posts about -177 errors but without enough detail.
Joe
--- End quote ---
I running Jason's mod and AFAIK this mod allows setarate corrections for separate apps. This puzzles me even more...
Miep:
--- Quote from: Raistmer on 21 Feb 2011, 02:51:48 am ---I running Jason's mod and AFAIK this mod allows setarate corrections for separate apps. This puzzles me even more...
--- End quote ---
You are still working with/against server side dcf estimates.
Plus while Jason's correction formula has a higher down slope than the original (iirc) it still needs time to correct for large changes - and you don't have the panic up correction of the original, but the same asymptotic bahaviour as for downwards corrections.
So unless something messed up the adcf value stored for the app in question (or your setup has changed) it has to be server side.
I'd edit the acdf to something more sensible and then run Fred's rescheduler to correct for the possible -177s.
Navigation
[0] Message Index
[#] Next page
Go to full version