BOINC 6.6.10 is available for Windows. As stated in other threads this is a Development version and may not work correctly.

At this pace, expect 6.6.11 tomorrow.

No release notes yet ...

Makes one wonder why ... :)

No release notes yet ...

Makes one wonder why ... :)

Another new one? One wonders if there is any remaining version control at Berkeley. :(

Oh well .......
____________

The Work Fetch Policy was completely changed for 6.6.*. It started out messed up, and with every "fix" it just gets worse. I would stay with 6.4.5 until someone gives the all-clear.
____________
Reno, NV
Team: SETI.USA

The Work Fetch Policy was completely changed for 6.6.*. It started out messed up, and with every "fix" it just gets worse. I would stay with 6.4.5 until someone gives the all-clear.

No wonder. Add in your cc_config.xml:

<log_flags>
<work_fetch_debug>1</work_fetch_debug>
<poll_debug>0</poll_debug>
<sched_op_debug>1</sched_op_debug>
</log_flags>

And look at that mess.
____________
Constant dripping wears away the stone. :)

Well, these are development versions. So after they made enough changes to the code they eventually have to create a new build and check out what they did. So many new versions just means they're hard at work.

MrS

For those that don't follow the boinc_alpha and boinc_dev mailing lists...

The last stumbling block would appear to be the long term debt (LTD) getting out of whack. They wanted to automatically correct them as they are inherited from the earlier versions of BOINC. As a result of the LTD's getting out of whack BOINC doesn't want to request work until it runs dry.

I suggested a button that would allow us to reset the LTD ... such a simple idea ... I wonder how long it will take before they come around to it ...

Um, not exactly ...

This is the kind of nonsense that gets done when simpler and easier ways (from the users perspective) would serve. So, now you have to edit a file, start the client, re-edit the file ... insane ...

Better than having to edit the client state file I suppose, but, just barely...

I also suggested a cross-tab report of the current internal accounting so that those of us that are seeing odd behaviors could actually provide meaningful information. The later 6.x clients have the "Properties" button on the project, but that means if you have a project load such as I do, well, 50 presses and lots of writing.

Update: 6.6.11 is out.

It doesn't add the tag to cc_config by default, so you are right Paul, its a manual process.

No word yet on what else is in this one.

Has anyone tried it yet?

I am certainly interested in being able to run a version where I don't have to set my resource shares at odd values just to make sure that the GPU projects (GPU GRid and MW) are always "starved" for resource and so that they will run full time...

I keep hoping that they will add the beginning code that will recognize the ATI cards so we can start to debug THAT ... sigh ...

Rats! My MW set-up is idle again ...

Quote from http://boinc.berkeley.edu/dev/forum_thread.php?id=2518&nowrap=true#23298:

- client: new work-fetch policy:

1) if an instance is idle, get work from highest-debt project, even if it's overworked.

2) if resource has a shortfall, get work from highest-debt non-overworked project

3) if there's a fetchable non-overworked project with no runnable jobs, get from from the highest-debt one.

(each step is done first for GPU, then CPU)

- client: fix work-fetch bug that caused infinite fetch; cleanup/reorganization of work fetch logic

- client: fix bug that can cause no GPU jobs to be scheduled even when a GPU is free.