I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

It's just a problem with BOINC and the debt system it uses. Try increasing the MW resource share - or down grade to a non 6.6.x version of BOINC. I'm using 6.4.5 with MW at 50% and BOINC just keeps enough work cached for it but at least it is always trying to crunch MW. Some others have downgraded all the wasy to 5.10.45.

I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

It's just a problem with BOINC and the debt system it uses. Try increasing the MW resource share - or down grade to a non 6.6.x version of BOINC. I'm using 6.4.5 with MW at 50% and BOINC just keeps enough work cached for it but at least it is always trying to crunch MW. Some others have downgraded all the wasy to 5.10.45.

Thanks Gas Giant, let me give it a try.

I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

It's just a problem with BOINC and the debt system it uses. Try increasing the MW resource share - or down grade to a non 6.6.x version of BOINC. I'm using 6.4.5 with MW at 50% and BOINC just keeps enough work cached for it but at least it is always trying to crunch MW. Some others have downgraded all the wasy to 5.10.45.

I tried BOINC 6.4.5 and it works ok, at least it's trying to crunch MW but after a day of work, BOINC started to download WU for the other projects and no longer request tasks for MW. I've to suspend all other projects to get BOINC to download MW's WUs again. Should I try a different BOINC version?

You need to roll back an earlier 6x version (6.2 or something like that) or 5.10 to get rid of that behaviour.

The reason is that with 6.4 and higher LTD is bounded at zero in the positive direction.

The problem comes about because the gate which determines when a project is LTD eligible for a work fetch is the negative of the Task Switch Interval you have set for the host. For example, if you have the default value of 60 minutes, then a project becomes able to fetch work when its LTD is greater than or equal to -3600 seconds.

The problem is that if you limit "positive" LTD to zero, any time a project (especially one with tight deadlines like MW) runs its LTD is virtually guaranteed to go more negative than -TSI pretty quick, and thus cut it off from getting more new work until another project starts running and gives the first one a chance start accumulating "positive" LTD again.

The net result is BOINC now has a tendency to load each project up to the max in sequence (weighted by Resource Share), run all the work out for that one, then sit idle until the other projects run long enough in turn to get it back over the fetch gate and repeat the cycle.

IMO, this was a really dumb idea, designed to address a problem which really doesn't exist if you take a long term view to things like Resource Share and Work Rotation mix.

Alinator

Since you can set debts using boinccmd, would a timed script event forcing MWs debts back to whatever they need to be work?

--set_debts URL1 STD1 LTD1 {URL2 STD2 LTD2 ...}
    Set the short- and long-term debts of one or more projects.
Note: if you adjust the debts of a project, the debts of other projects are changed, so if you want to set the debts of multiple projects, do it in a single command.

And is there a flavor of 6.2.x that's preferred? I'm going to try 6.2.19 the last documented release before 6.3.x and see what it does.

Edit: 6.2.19 looks to be doing to exact same thing 6.3.36 is. If I cycle the client it will fire MW units along side the 4 CPU apps but as soon as it finishes them and downloads more it goes back to idling until it trips their "turn" again even though they shouldn't be CPU bound.

You could try setting the preference "Switch between applications every" from its default of 60 minutes to something like 5 minutes. Hopefully that way it might trigger the MW app after 5 minutes of non-crunching.