I am running Seti Beta (0 weight), PrimeGrid (100 weight), and CSG (10000 weight). When it came time to fetch new work, Boinc grabbed a Seti task rather than a PG task. This occurred when I pausing a CSG task (Seti and PG had no paused tasks) in order to grab a PG task for an empty thread. The client is Boinc 7.4.42.

This is the first time I ever saw Boinc grab a task for a 0 weighted project over a 1+ weighted project. I have always worked under the assumption that 0 weighted tasks are only fetched if there were any idle threads and after requesting tasks from any projects weighted 1 or above. Yes I had one thread free so getting a Seti task was not out of bounds.

And I checked the properties and the scheduling was -1000.00 for the Seti and -1069.58 for the PG. So yes the priority is seemingly for the Seti project. However, in other versions of Boinc (7.2.42 for example) even 1 weight projects with priorities as low as -30000.00 send get requests before the 0 weight/-10000.00 projects. Also I checked that there was no work fetch deferral for PG.

So I am confused as to why there was no request to get tasks from PG prior to the Seti request.

I am running Seti Beta (0 weight), PrimeGrid (100 weight), and CSG (10000 weight). When it came time to fetch new work, Boinc grabbed a Seti task rather than a PG task. This occurred when I pausing a CSG task (Seti and PG had no paused tasks) in order to grab a PG task for an empty thread. The client is Boinc 7.4.42.

This is the first time I ever saw Boinc grab a task for a 0 weighted project over a 1+ weighted project. I have always worked under the assumption that 0 weighted tasks are only fetched if there were any idle threads and after requesting tasks from any projects weighted 1 or above. Yes I had one thread free so getting a Seti task was not out of bounds.

And I checked the properties and the scheduling was -1000.00 for the Seti and -1069.58 for the PG. So yes the priority is seemingly for the Seti project. However, in other versions of Boinc (7.2.42 for example) even 1 weight projects with priorities as low as -30000.00 send get requests before the 0 weight/-10000.00 projects. Also I checked that there was no work fetch deferral for PG.

So I am confused as to why there was no request to get tasks from PG prior to the Seti request.

My guess is that they have made a change in the latest version. Someone assumed -1000.0 was so negative that in no case would a project with a share >0 ever be that negative. Bad assumption. They really should have picked -MAXFLOAT. So yes, I think it is a bug.

---