I got this message THIS MORNING! I had Collatz in no new tasks and suspended mode and it was at 10% anyway. Moo is set at 30%, they are the ONLY two gpu projects on the machine! Is this a project thing fighting among themselves over which gets crunching time on my pc?!!! I have now removed Collatz but AM NOT HAPPY!!! I PREFER to keep two projects already attached and ready for when my primary choice goes down!

PS...I JUST did a manual update and got this:
9/6/2012 9:11:11 AM | Moo! Wrapper | Not requesting tasks: project is not highest priority

The ONLY other project connected is WCG and it has 100% priority but is cpu ONLY!!!

PS...I JUST changed my Moo priority to 1000% and did a manual update and got this:
9/6/2012 9:14:47 AM | Moo! Wrapper | Not requesting tasks: project is not highest priority
AGAIN!!!!

Hey,

I've seen a lot of change log entries in v7 client that indicate there's a lot of work going on with work scheduling there. I remember seeing something about this "highest priority" thing (not sure if they fixed that or added it).

Are you still having problems since I updated the BOINC Server code to match? What BOINC Client version are you running?

-w

Hey,

I've seen a lot of change log entries in v7 client that indicate there's a lot of work going on with work scheduling there. I remember seeing something about this "highest priority" thing (not sure if they fixed that or added it).

Are you still having problems since I updated the BOINC Server code to match? What BOINC Client version are you running?

-w

That particular pc is running Boinc 7.0.31 and I have not checked it yet today, I will do it right now:
I JUST did and I am STILL seeing this:
9/10/2012 7:20:22 AM | Moo! Wrapper | Not requesting tasks: project is not highest priority.
I on the East Coast of the US.

So NO not fixed for me. I AM getting units and DO seem to have plenty, so I am not SURE what the message is telling me except 'not right now'. It is a machine with dual AMD 5770's in it that just will NOT run Moo unless I run an app_info file that forces Moo to run on each gpu separately.

Just updating the thread:
I JUST updated Boinc to version 7.0.36, a Beta, and go this:
9/16/2012 9:01:59 AM | Moo! Wrapper | Not requesting tasks: project is not highest priority

As I said before I am NOT out of tasks but the error message itself is what bothers me. I DO seem to get tasks as needed, but get the above message when I do a manual update.

Hello,

Maybe this post helps explaining the new scheduling feature of BOINC Client v7: http://boinc.berkeley.edu/dev/forum_thread.php?id=7467. There's also some links that are worth following for more information about new work fetch settings.

So it seems to be a normal "error" to get in v7 when BOINC Client doesn't want to fetch work for that project because some other project deserves crunching time at the moment. Recommendations for a remedy range from waiting few weeks to see how things balance out to fiddling with work fetch preferences in the client. In any case they recommend to stop micromanaging the client work buffers and just let BOINC Client do it's thing.

You could also enable work_fetch_debug debug flag to hopefully see why BOINC Client makes the decisions that it makes. For more information, please read http://boinc.berkeley.edu/wiki/Client_configuration#Logging_flags.

So to summarize, this is not something a project can control from server side or even in application code, AFAIK. It's all handled internally in the BOINC Client.

-w

Hello,

Maybe this post helps explaining the new scheduling feature of BOINC Client v7: http://boinc.berkeley.edu/dev/forum_thread.php?id=7467. There's also some links that are worth following for more information about new work fetch settings.

So it seems to be a normal "error" to get in v7 when BOINC Client doesn't want to fetch work for that project because some other project deserves crunching time at the moment. Recommendations for a remedy range from waiting few weeks to see how things balance out to fiddling with work fetch preferences in the client. In any case they recommend to stop micromanaging the client work buffers and just let BOINC Client do it's thing.

You could also enable work_fetch_debug debug flag to hopefully see why BOINC Client makes the decisions that it makes. For more information, please read http://boinc.berkeley.edu/wiki/Client_configuration#Logging_flags.

So to summarize, this is not something a project can control from server side or even in application code, AFAIK. It's all handled internally in the BOINC Client.

-w

THANK YOU for that! I have too many pc's here at home, mostly rebuilt from other pc's parts, to not micromanage them. When I don't micromanage them they tend to turn off and not crunch. I am okay with the error, I have been getting work just not when I do a manual connection. I may do the debug flag just to figure it out but Moo is the ONLY gpu project I run on most of my machines and therefore it doesn't seem reasonable that some other project has a higher priority, unless they are including the cpu in the computations which seems silly! I thought a while back they separated the two from each other in their cache handling.