I have some strange "problem":
When I get a task from milkyway@home, it says that it needs 400 to 500 hours to complete. Like today (8/12/2008) I have a task that should complete before 11/12/2008, but it will take about 480 hours. The Boinc manager runs it in high priority (480 hours and it has to be finished in 3 days!). But after little more than 1 hour it has finished.
Is this a bug or is this a way to 'speed up' the calculation of the milkyway@home-tasks, giving them higher priority over other projects?

I have some strange "problem":
When I get a task from milkyway@home, it says that it needs 400 to 500 hours to complete. Like today (8/12/2008) I have a task that should complete before 11/12/2008, but it will take about 480 hours. The Boinc manager runs it in high priority (480 hours and it has to be finished in 3 days!). But after little more than 1 hour it has finished.
Is this a bug or is this a way to 'speed up' the calculation of the milkyway@home-tasks, giving them higher priority over other projects?

It's a BOINC 'feature', not to do with MW. It will sort itself out after you've run a few MW WUs.

---

What is a few WU's?.
I already run at least 10 WU's in the last week or 2 and this still happens.

@ Kriki

First , Welcome to Milkyway@home !!

And now back to your problem , some guys from another project they had some similar problems with the 6.2.19 Boinc core client and as i see you are using the same version.

Sometimes it helps just to let run a project till boinc will adjust the real estimated time some wus they need. For some reason your boinc calculates too big crunching time for the MW wus and sets automatically these wus in high priority in order to finish em before the dead line.

---

What is a few WU's?.
I already run at least 10 WU's in the last week or 2 and this still happens.

With that much of a difference it may take many tasks before it straightens out. The DCF moves in three different modes; if it is too low it immediately jumps up to the new estimate. If it is somewhat high it moves 10% of the difference at a time, usually 10-20 tasks will be enough to fix this amount of difference. If the estimate is very high it moves 1% of the difference at a time, in this case it can take 100s of tasks to get it straightened out. It was done this way prevent some tasks ending quickly compared to other tasks of the same type from changing the DCF too quickly.

The client will eventually straighten out, until then you see it running Milkyway tasks in high priority mode then running other projects for a time until the CPU debt is paid back. Detaching and reattaching should fix it if you do not want to wait.

---

BOINC WIKI

BOINCing since 2002/12/8

Thank you for the information.
I will just wait until the 'problem' fixes itself.

What is a few WU's?.
I already run at least 10 WU's in the last week or 2 and this still happens.

With that much of a difference it may take many tasks before it straightens out. The DCF moves in three different modes; if it is too low it immediately jumps up to the new estimate. If it is somewhat high it moves 10% of the difference at a time, usually 10-20 tasks will be enough to fix this amount of difference. If the estimate is very high it moves 1% of the difference at a time, in this case it can take 100s of tasks to get it straightened out. It was done this way prevent some tasks ending quickly compared to other tasks of the same type from changing the DCF too quickly.

The client will eventually straighten out, until then you see it running Milkyway tasks in high priority mode then running other projects for a time until the CPU debt is paid back. Detaching and reattaching should fix it if you do not want to wait.

If you manually edit 0<DCF<<1 its fixed within ±5% after one task.
Detaching and reattaching to this project resets DCF to 1 and gives the 5 to 10 hr estimates again.

---