I am running Seti@Home, SIMAP, and Climate Prediction. My preferences are set for equal sharing between the three and to change projects every hour but Climate Prediction always starts running at high priority and the sharing stops. To get the other two projects to run I have to periodically suspend Climate Prediction.

Occasionally SIMAP will also run at high priority.

Does anyone know why this is happening? What controls priority?

Thank you.
Gary Bouskill

This means that BOINC sees a possible deadline problem. In that case it gives tasks more CPU time than their resource share would normally allow. Often once you get farther into the CPDN model the estimated time to completion will be more accurate and the client will no longer be as concerned about missing the deadline. In the long run your resource shares will be honored by not downloading more tasks from projects that have used more than their share of the CPU.

I suspected that might be the case. The project has a completion date of 12/01/08 with a lot of hours yet to run to completion (Progress 29%). I'll just leave it running for awhile.

Thank you for your reply,
Gary

Just remember, if one of the other projects gets into deadline trouble, that project should kick into high priority, so it's not like the Climate Prediction high priority will result in late WU's, just no more WU's while it's in high priority.

Do know that CPDN is the only project that allows their models to continue after the deadline. You'll still get credit for the trickles you send in. Only BOINC will complain that the task is past deadline and that you should consider canceling it. If you don't want to, then don't.

climate is not the only project to grant credits after the deadline. Depspid is another one, and there ARE others out there.

I know that most projects that have a minimum quorum will usually give you points, if you get it in before the quorum is made.