No, the only way to individually balance is using app_config.xml and if you are the proud owner of multiple crunchers, to assign different profiles to the various devices. Other than an overall task volume control that pushes an N number of tasks per project into the shared memory [periodically manually adjusted based on current average runtime per task], there's no mechanism in the distributor system.

Effectively, if you choose sub1+sub2 out of sub1-sub5, you'll get whatever is in the feeder at the time of the work request of those 2 subs. BOINC requests N seconds of work and that is what you get if the feeder has it, in whatever available mix, at the overall set pool weights [if both are available at the weight set]. Effectively, exclusive hunters draw all at this time lof the low share/low priority FAHB, so my OET1+FAHB profile is only receiving OET1. The device set to only receive FAHB has no trouble to keep the buffer backfilled, set low as the short deadline makes them go into high priority very quickly when not started... EDF panic.

yes there is!

U go to WCG site & select:
- FAHB project to execute
- also to get any other projects that might be available

so u will get all jobs, exept CEP2...'cause u haven't got a good enough exipment for CEP2!


p.s. see if u can put on WCG site to give u 0 jobs of CEP2...that would also help!

Have a think about the published minimum system requirements for CEP2 and whether you could make use of that info

Sounds like a multi-threaded app would be up your alley... Too bad WCG doesn't use any, but there are other BOINC projects that do. I have become a fan of them because of the reduced memory overhead, but there are others who prefer having their cores split up with a number of projects.