Thanks Fred
From my own investigations, REC for all projects goes down whenever the boinc client is running, at a rate defined by the global half life setting. Not actually sure what triggers it being recalculated, but appears to be at any job completion, and probably at other times too. I think this is the REC Time field. Suspending a project doesn't affect the recalculation. When a job runs it increase the REC for the project of the job in relation to the number of resources and how long it runs for.
The job scheduler appears to take a job from those already waiting from the project with the lowest (REC/Resource share) subject to other constraints (eg deadline, max concurrent etc)
I'm asking for this so I can make an estimate as to when the ready workunits are going to get naturally processed (vs. getting scheduled due to approaching deadline) - the work fetch process is spectacularly poor when it comes to projects with substantially different resource shares (it fetches too much work for those with a small allocation)
On Win10Home here, and the first couple of attempts to get round the non-signed app didn't work (failed in the DISM part), so haven't got the .js running yet, I'll keep working on that. For the meantime still on 1.85
From my own investigations, REC for all projects goes down whenever the boinc client is running, at a rate defined by the global half life setting. Not actually sure what triggers it being recalculated, but appears to be at any job completion, and probably at other times too. I think this is the REC Time field. Suspending a project doesn't affect the recalculation. When a job runs it increase the REC for the project of the job in relation to the number of resources and how long it runs for.
The job scheduler appears to take a job from those already waiting from the project with the lowest (REC/Resource share) subject to other constraints (eg deadline, max concurrent etc)
I'm asking for this so I can make an estimate as to when the ready workunits are going to get naturally processed (vs. getting scheduled due to approaching deadline) - the work fetch process is spectacularly poor when it comes to projects with substantially different resource shares (it fetches too much work for those with a small allocation)
On Win10Home here, and the first couple of attempts to get round the non-signed app didn't work (failed in the DISM part), so haven't got the .js running yet, I'll keep working on that. For the meantime still on 1.85