Hello,

on friday boincmanager showed me an outage on the milkyway-server (project down for maintenance). So my backup-projects starts working (first donate, than distrrgen). After about one hour I received new WU from milkyway, but from then all tasks running in high priority, although milkyway is the only gpu-project currently running (by now distrrgen is backup-project with resource share 0).

This high priority issue remains since more than two days.

BM 7.0.25 (Win 7)

Do you have any suggestions for me?

Thanks

Nowi

---

Having same issue with 7.0.24 with Linux.

I get same problem with CPU tasks

BM 7.0.25 Win XP

Hello,

on friday boincmanager showed me an outage on the milkyway-server (project down for maintenance). So my backup-projects starts working (first donate, than distrrgen). After about one hour I received new WU from milkyway, but from then all tasks running in high priority, although milkyway is the only gpu-project currently running (by now distrrgen is backup-project with resource share 0).

This high priority issue remains since more than two days.

BM 7.0.25 (Win 7)

Do you have any suggestions for me?

Thanks

Nowi

Reduce your cache size, Boinc now thinks you have too much work and can't finish it before the deadlines. It could also be the estimated time to completion could be waaaay off and Boinc will fix that on its own. Unless the high priority is a problem for you, just ignore it, it will balance itself out in a few days.

Who actually assigns the high priority designation? Is it BOINC or does the application itself do it?

Please see this thread for information and possible solutions, but let's keep the discussion here.

Please see this thread for information and possible solutions, but let's keep the discussion here.

Thanks.

Do the BOINC people concur that this is a bug and plan to fix it soon?

Hi people,

I posted about this on the BOINC message board "Questions and Problems" "BOINC 7.0.25 High Priority Problems" and got the answer that the patch for this bug is included in 7.0.27. It seems too complex to go back to 6.xx so I may just wait until that is released. As yet I do not know when that will be.

John

Hi John,

thank you for this information!

Anyone who wants can find new versions here: http://boinc.berkeley.edu/dl/?C=M;O=D

---

Who actually assigns the high priority designation? Is it BOINC or does the application itself do it?

Boinc does it based on your history of time it took to crunch your returned units, over time Boinc WILL fix it on its own. To view a projects DCF just go into the Boinc Manager, down by the clock, and click on the projects tab, then a project, then the properties button in the left panel. The DCF is listed at the bottom. A DCF of 1.0000 is the starting point for every project but changes based on how long YOUR pc takes to crunch a unit. For instance I only have one project on the pc I am typing this one and the DCF is 1.0689, that is because I use the pc for things besides JUST crunching, like typing on the forums! That slows down the crunching for the unit I am working on right now which raises my DCF a teeny tiny amount. Each project has a time estimate of how long they think a unit will take to crunch, it is just an estimate, but if your pc takes longer, or is faster, than they think there needs to be a way to maintain your workunit cache in relation to that time. So Boinc has this Duration Correction Factor, or DCF, to take that into account, so if a project thinks a unit will take 1 hour but your pc only takes 30 minutes, how do you get a 1 day cache of work? Thru the DCF telling the project you need twice as much work as the next person. Same thing as now...Boinc is recognizing, thru an error, that the units may not be done before their deadlines so it is increasing their priority within the pc to use more cpu time than it normally would, so High priority!

mikey, thanks for your explanations. As far as I can tell that's all correct except the assumption in the last sentence. Unfortunately this whole DCF thing does not apply here. BOINC is moving away from the DCF concept and Milkyway seems to be an early adopter. That's why we got bitten by this non-dcf bug and other projects did not.

The problem is that the boinc client doesn't even consider normal priority if the project doesn't have a DCF below 90. But in BOINC 7.0.24 and later, Milkyway does not have a DCF at all and BOINC gets the hiccups from that. In future releases this will be "DCF below 90 or no DCF", so non-dcf projects' tasks will be handled normally then.

mikey, thanks for your explanations. As far as I can tell that's all correct except the assumption in the last sentence. Unfortunately this whole DCF thing does not apply here. BOINC is moving away from the DCF concept and Milkyway seems to be an early adopter. That's why we got bitten by this non-dcf bug and other projects did not.

The problem is that the boinc client doesn't even consider normal priority if the project doesn't have a DCF below 90. But in BOINC 7.0.24 and later, Milkyway does not have a DCF at all and BOINC gets the hiccups from that. In future releases this will be "DCF below 90 or no DCF", so non-dcf projects' tasks will be handled normally then.

That makes sense, Boinc is always changing! My pc's with MilkyWay NOT currently actively getting units but still attached to it AND running 7.0.25 do still show a DCF number when clicking properties in the Boinc Manager, are you saying that number is just for show?

do still show a DCF number when clicking properties in the Boinc Manager, are you saying that number is just for show?

I think it is unused in projects like Milkyway and just hasn't been removed (yet?) for simplicity. Does it change? I noticed the estimated run times of queued tasks no longer do.

Hello,

on friday boincmanager showed me an outage on the milkyway-server (project down for maintenance). So my backup-projects starts working (first donate, than distrrgen). After about one hour I received new WU from milkyway, but from then all tasks running in high priority, although milkyway is the only gpu-project currently running (by now distrrgen is backup-project with resource share 0).

This high priority issue remains since more than two days.

BM 7.0.25 (Win 7)

Do you have any suggestions for me?

Thanks

Nowi

Set ALL your projects to "no new tasks".
Let them all complete and report.
Then revert to version 6 and download new work.
A technical code issue in version 7 causes this problem and will be fixed in a newer upcoming version in the future.

Thanks for all your answers!

In fact running of M@H-tasks in high priority has become more and more an "optical" problem for me. Roll back to version 6 isn´t really an option, because I´m running long lasting CPDN tasks, which will be lost then.

I will wait for the fix in 7.0.27.

---

do still show a DCF number when clicking properties in the Boinc Manager, are you saying that number is just for show?

I think it is unused in projects like Milkyway and just hasn't been removed (yet?) for simplicity. Does it change? I noticed the estimated run times of queued tasks no longer do.

I don't know I am not getting any tasks right now as I working on other goals at the moment. And Berkeley HAS done things like that in the past, leave things in but don't use them I mean.

do still show a DCF number when clicking properties in the Boinc Manager, are you saying that number is just for show?

I think it is unused in projects like Milkyway and just hasn't been removed (yet?) for simplicity. Does it change? I noticed the estimated run times of queued tasks no longer do.

I don't know I am not getting any tasks right now as I working on other goals at the moment. And Berkeley HAS done things like that in the past, leave things in but don't use them I mean.

I changed my settings to allow new work and got 28 workunits immediately! I will finish them and go back to what I was working on.

I have just downloaded BOINC 7.0.27 and the "high priority" tag has disappeared. I have not had time to fully test it but so far - so good

John

I have just downloaded BOINC 7.0.27 and the "high priority" tag has disappeared. I have not had time to fully test it but so far - so good

John

Here is the change log page:
http://boinc.berkeley.edu/dev/forum_thread.php?id=6698&nowrap=true#43938

There are a BUNCH of them!!

Set ALL your projects to "no new tasks".
Let them all complete and report.
Then revert to version 6 and download new work.
A technical code issue in version 7 causes this problem and will be fixed in a newer upcoming version in the future.

Yeah, no. If milkyway is the program that's malfunctioning, then I won't be not doing other projects for its sake. Instead, rather, I'll just stop crunching for Milkyway.