Would like info on GR non-configurable properties

  
Michael J Lewchuk
ID: 68330
Posts: 1

Hello.

I would like information on what the following mean: Projects: CPU Scheduling Priority, Projects: CPU Work Fetch Priority, and how task CPU time estimates are calculated.  Note: it would also be nice to put them in the GR user's manual.

GR once bumped up my POEMs to High Priority (I don't know why), then it stopped doing that.  Does this control the priority each project gets in the CPU round-robin or does it actually control the task process priority or both?

I would guess CPU Work Fetch Priority is a measure the core servers use to determine how much work to feed your computer.  Does it also control priority of projects versus other projects?

The third thing is CPU time estimates.  I notice that POEM and Malaria seriously overestimate their time requirements,usually 50% more than needed and once 100x as much as needed (2 tasks had an estimate of 5 days each, they both ran in 2 hours), while Docking, WCG, and Rosetta seem to underestimate by 5-10% (probably due to me sucking up valuable CPU cycles typing at the keyboard and using my mouse).

Thanks.

(Wednesday, November 16 11, 4:11 AM)
Matt
ID: 21503
Posts: 326
GR lets you set "resource share": this setting allows you to specify what portion of your computer's time is allocated to each of your projects.  

To figure the proportion of time allocated to a specific project: take the resource share for that project as the numerator, and then add together the resource shares of all your projects and take that as the denominator -- this ratio is the percent of time that will be allocated to the one project.  (Subject to change if one or another project does not have work available.)

Work fetch policies and time estimates are determined by BOINC itself and/or individual projects; GR does not control these.
(Sunday, November 20 11, 11:54 PM)
Post   Previous   Page 1 of 1   Next