If I leave things normal, Rosetta has all the task slots taken up and Einstein seems to wait for ever to get a slot. I set resource share to 50 w/Einstein at 100 to no avail. Rather than go in and suspend the Rosetta tasks, I have taken to setting Rosetta to 'no new tasks' to give Einstein some run time. I really would prefer not to give up and remove Rosetta like I had to do with the Climate program. Is there something I can do to balance the programs task-sharing?

Adding another project to a computer will make BM try to catch up and run the new project more until it reaches the given resource share ratio. You can let it go and it will work itself out in the long run or manually adjust R@H lower for now and gradually make it our desired ratio.

BOINC Manager controls which tasks are running. It is because R@h is newly added that BOINC Manager is running more of it. The same thing (new project appearing to be too aggressive) happens to the R@h user that later adds Einstein.

It will take a day or so to settle in. The best approach is to let BOINC Manager run without trying to manually force it to do something differently. Otherwise it is left trying to adapt to a constantly changing set of goals.

The resource shares used in BOINC Manager should be examined over the course of a day or a week, not the course of an afternoon.

---

Rosetta Moderator: Mod.Sense

BOINC averages the number of WU over a period of time. When you add a new project, it will try to crunch the job mix to MEET the the WU mix defined. I think they balance on the number of WU and not on CREDITS. If you have 2 projects equally weighted, BOINC will try to match the number of WU.

A couple things you can use to get stable faster.
1. Select the shorter 1 hour Rosetta WU until it stabilizes. You will complete more WU more quickly.
2. Change the default 10 day window for calculating averages so the window is shorter.


<rec_half_life_days>X</rec_half_life_days>
A project's scheduling priority is determined by its estimated credit in the last X days. Default is 10; set it larger if you run long high-priority jobs.

BOINC averages the number of WU over a period of time. When you add a new project, it will try to crunch the job mix to MEET the the WU mix defined. I think they balance on the number of WU and not on CREDITS. If you have 2 projects equally weighted, BOINC will try to match the number of WU.

A couple things you can use to get stable faster.
1. Select the shorter 1 hour Rosetta WU until it stabilizes. You will complete more WU more quickly.
2. Change the default 10 day window for calculating averages so the window is shorter.


<rec_half_life_days>X</rec_half_life_days>
A project's scheduling priority is determined by its estimated credit in the last X days. Default is 10; set it larger if you run long high-priority jobs.

BM should be scheduling by time, right? BM has no idea what credit will be. I would expect if R@H takes 1 hour and E@H takes 2 hours then 2 R@H tasks will run and 1 E@H will run as the resource share levels out. At that point a host's queue would have 2x R@H than E@H and run them 2:1 giving and equal resource share. Assuming the same share is given to each project.

I have over 260k work units with R@H this is not a new issue; but I will monitor the user averages rather than just look at the active task list. Maybe my random glance that always shows R@H hogging the CPU is not a valid test of how the 2 play together.

BOINC Manager controls how many tasks are downloaded and which ones run. Project's don't work either each other or your PC. This is all controlled by BM.

I've noticed the same thing & it looks like it's due to Rosetta WU's having Very short deadlines. I'm running SETI & Rosetta - new WU's from Rosetta have a deadline of 11/7 (3 days from now), while the new SETI WU's have a deadline of 12/27 (~ < 2 months).

Do these Rosetta WU's Need to have a deadline that is very short?

Franko

Do these Rosetta WU's Need to have a deadline that is very short?

Yes. R@h tasks have deadlines that reflect the needs of the project and the specific tasks. 3 days is the shortest deadline used by R@h at this point.

---

Rosetta Moderator: Mod.Sense

Good to know, thanks!!

Franko

Do these Rosetta WU's Need to have a deadline that is very short?

Yes. R@h tasks have deadlines that reflect the needs of the project and the specific tasks. 3 days is the shortest deadline used by R@h at this point.

Setting Rosetta's resource share to 0 has made it play nicer with my higher priority projects that will go days without any work then hit in bursts that forces the backup Rosetta WU's into 'waiting'.
Still have to delete some Rosetta when high priority project WU come in cause of the short Rosetta deadline.