I have 4 projects across 3 hosts, OSX 10.7, OSX 10.8 & Windows 7. My Project level resource allocations are 2500, 1000, 2500, 4000 for ClimatePrediction, Einstein, LHC & SETI respectively; but the client is reporting 100, 1000, 2500, 4000 thus changing the %age allocation; ClimatePrediction is getting about 1.3% when it should be getting 25%. I've verified the allocation at the host level and the values are all correct online.

I tried resetting detaching all hosts (2 at this point) from ClimatePrediction, did a manual sync, project dropped off list, I then did an attach all hosts and repeated the sync, the values were then correct. At this point (9/6/2012 approx 1700 UTC) I added the 3rd machine OSX 10.7, my new work laptop which replaced another host that I manually deleted. On joining it to BAM it was seeing the values 100, 1000, 2500, 4000.

I've tried detaching/attaching project, update/reset/remove & disconnecting/reattaching to BAM Several times without any affect on the value seen by the client. When I forced a sync on the machine (OSX 10.8) that updated to the correct values it has now reverted to the 100, 1000, 2500, 4000 pattern.

I also tried resetting all values to 1250 and forced a sync, the values did not change.

I don't know if this is a bug or an ID-10-T user issue but it's bugging (Oh! what an apt word ) the do-do out of me! Any ideas on how to fix this welcome.

Thanks

Ray

I got around the immediate problem by scaling off of the 100 it kept setting ClimatePrediction to, using the values 100, 10, 100, 160 the distribution is now correct but there definitely seems to be a bug in the resource allocation process.

You could say that.

First, consider that there are multiple places to allocate your resources: BAM!; your group list (or host list, depending on your preferences) settings in BAM!; your 'My Projects' within BAM!; and let's not forget each and every project.

Considering all of these things, remember that BAM! does NOT synchronize any of these settings within itself (e.g. your group list may have Asteroids @ 100, 'My Projects' might have a setting of 5000, and 'Host list' has a setting of 2500. These are separate entries, and they appear to have a hierarchy of preference as follows:

1. Group List.
   
2. Host List. (Each host has its own priority list)
   
3. My Projects.
   

So, in the above case/example, since there did exist an entry for Asteroids in 'Group List', BAM! would apply a priority of 100. If the same host/pc were removed from the group in question, the priority would then be 2500 based upon the entry of the 'Host List'; and lastly, if a brand new host were to attach to this BAM! for the project Asteroids, and it did not have a 'Host List' entry, it would receive the default, 'My Projects' setting of 5000.

Okay, now that we have BAM! sorted out (for the most part), we do have one more entry in the equation that needs to be addressed, or at least understood when we start seeing different values show up on our BOINC Manager/BOINCTasks display. The project itself allows you to enter priority values in the section normally (WCG being one exception) labeled, 'Preferences for this Project'. Here you can assign a priority to the specified project based upon a hosts venue. Normal values are Home, Work, School (some projects have added 'Mobile' as well), which allow you to 'group' your hosts by venue to run different wu, or to fun only gpu/cpu, or just control the priority. Note to be sure to not only assign your priority in the preferences, but be sure to set your host to the correct venue in the 'Computers on this Account' section of your project.

It should be noted that after your host is synchronized, and updates with the project, the project priority USUALLY will supersede any of the values you had entered in BAM!

I hope that this helps. I have vested many a hour trying to make the priority thing work, and the above are the findings. Good luck with your projects. If you find anything incorrect, or a better way to run BAM!, do share, either here, or PM me.

Phil

You must be pretty bored if you're scraping the barrel for a year-old post...