BOINC 7.0 does not work this way. It will only fetch work when the total work cache is below that of the minimum work buffer value and then it will only fetch work from the project with the highest priority (priority == 0, or close to it, like -0.05), and only if that project does not have work, will it fetch work from the next, and the next, etc.

OK, just to clarify, is the work cache you're talking about here an aggregate, so across all projects, or does this algorithm apply to each project individually?

If it's over all projects, then one project like CPDN with massive WUs will always have work well beyond the minimum work buffer value, and so BOINC would not be motivated to go fetch anything new from other projects. This is pretty consistent with the behaviour I'm observing.

If it's per individual project, then I have a dilemma, because I can't see that behaviour happening.

---

squeak

I have 7.0.27 installed and it seems to be fetching, albeit selectively which I gather is now the norm, even with the cc_config file in place. So I guess someone has figured it out somewhere.

Thanks to whomever.

;-)

Interesting!

Where did you find 7.0.27? I appreciate that it's still an alpha release, but I'm presuming that if I try it and decide it's a bit buggy, I can still revert to 7.0.25 (is this still true?)

---

squeak

Where did you find 7.0.27?

Try this link.

I appreciate that it's still an alpha release, but I'm presuming that if I try it and decide it's a bit buggy, I can still revert to 7.0.25 (is this still true?)

Yes, only returning to 6.x versions is a little more complicated. ;-)

Gruß,
Gundolf

Sorry not to reply sooner but sleep got in the way. I see you have the link.

A question for anyone....I assume if one chose to revert to (say) 7.0.25 in order to get back the old-style polling, that eventually there would be problems anyway as projects are forever reminding one to update BOINC. True or false?

Can one simply install it over the top of a higher version and revert that way?

Sorry not to reply sooner but sleep got in the way. I see you have the link.

A question for anyone....I assume if one chose to revert to (say) 7.0.25 in order to get back the old-style polling, that eventually there would be problems anyway as projects are forever reminding one to update BOINC. True or false?

Can one simply install it over the top of a higher version and revert that way?

Yes, the Windows installer does allow that - I take it you're talking Windows, from your avatar.

You'll find that a downgrade installation ends with an error. Just re-run the installer (so dowdload it to your local disk, and run from there), and choose the 'repair' option that it'll offer. It's always worked at the second attempt, for me.

Thanks Richard. Yes, Windows. I'll try to resist the temptation to wind back the clock and see what transpires with this new 'improved' version.

I'm not a fan of this 'selective' work fetch which seems to totally ignore most of my projects, most of the time, but at least it's fetching work now with that cc_config entry, whereas before, with 7.0.26, it wasn't.

I fail to understand how Boinc is 'thinking' now. I have hardly any work on hand (4 WU's yet my processor can handle 8 simultaneously and often 1 or 2 more if the GPU is involved) yet it's only polling certain projects and not others.
My Mr. Spock alter-ego tells me that's not logical, at all.
If I manually poll for more work from all of my 16 projects - nothing, which I refuse to believe is true, but I guess I could be wrong, however it would be nice if Boinc would do that for me.
I know that the new system has been explained ad nauseam elsewhere but I'm afraid it just doesn't make sense to me.
Can anyone explain it in layman's terms?

---

Peter
Toronto, Canada

OK am trying to figure this out.

'Maintain enough tasks to keep busy for at least' (lower threshold)
'... and up to an additional' (upper threshold)

Set the first to 2 days (previously blank as I am always connected) and the second one to 1 day although some projects have different wording on that first one (Connect to....) and now I seem to be getting work.

Sorry to keep posting new posts but the Edit button disappears too rapidly.

The bug here is that you're still expecting BOINC 7.0 to work like previous BOINC versions did, where it will fetch work for whatever project e.g. when it's just uploaded & reported work for that project. Sort of to top off the cache all the time.

BOINC 7.0 does not work this way. It will only fetch work when the total work cache is below that of the minimum work buffer value and then it will only fetch work from the project with the highest priority (priority == 0, or close to it, like -0.05), and only if that project does not have work, will it fetch work from the next, and the next, etc.

Found this thread to be related to a problem I have. Runnig BOINC 7.0.28, win7 x64, 2 projects: GPUGrid and SETI@Home, "5" GPUs: two GTX 690s ("4" GTX 680s) and 1 GT 640. Here is my config file:

<cc_config>

	<options>

		<use_all_gpus>1</use_all_gpus>

		<ncpus>0</ncpus>

		<report_results_immediately>1</report_results_immediately>

		<exclude_gpu>
			<url>http://www.gpugrid.net/</url>
				[<device_num>1</device_num>]
		</exclude_gpu>

		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>0</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>2</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>3</device_num>]
		</exclude_gpu>
		<exclude_gpu>
			<url>http://setiathome.berkeley.edu/</url>
				[<device_num>4</device_num>]
		</exclude_gpu>

		<max_file_xfers_per_project>4</max_file_xfers_per_project>

	</options>

</cc_config>

Which means I am using the GT 640 (device 1) for SETI@Home and the two GTX 690s (devices 0, 2, 3 and 4) for GPUGrid. The problem is:

GPUGrid gets a full workload (the 4 devices are working with one workunit each) for about a day or so. The next day GPUGrid only crunches 2 workunits, thus leaving the other 2 devices sitting idle. This cycle repeats itself indefinitely.

I would love to know a workaround for this issue. I am not running 2 different instances of BOINC, but would consider doing so if it is the only way for crunching at all times my GTX 690s. I have set a project resource share 50-50 (that is, 100 each).

Any ideas?