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 ... :)

Changelog 6.6.10

At this pace, expect 6.6.11 tomorrow.

[sarcasm]
I like the change log. More debugging messages for work_fetch. So they have obviously sorted out the work_fetch changes then.
[/sarcasm]

---

BOINC blog

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.

Or 6.5.0 ... this version is my standard ... heck, it seems to work Ok with my brand shiny new ATI card and Milky Way tasks too ...

I don't know what my daily production will be ... but, hopefully it will be worth the investment ... initial indications are that it will be ... best of all, I got a 4870 for the price of a 4850 ...

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. :)

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

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

---

Scanning for our furry friends since Jan 2002

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

Agreed. Not sure why that's so hard for folks to figure out....if it was easy--it'd be done already...

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.

When I installed 6.6.10 I reset my LTD's manually and I haven't (so far, touch wood) had any issues with it.

We'll have to wait and see what the next version brings.

---

BOINC blog

We received news that version 6.6 once debugged should be the good one.
Let's see.

gdf

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 ...

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 ...

But you don't want it getting reset all the time by people who don't understand what LTD gets used for. Also you'd have to get them to press it when they change over to the newer version, if it needs to be reset.

You could put it under Advanced -> Options or somewhere like that, but even then it can get used when it doesn't need to be. And for those "set and forget" types they aren't going to press it.

My suggestion was to get boinc to do it when it detects the version change. That way no manual intervention is required.

---

BOINC blog

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 ...

It looks like your suggestion is accepted. A new option for 'cc_config.xml' has been created. The following text is from http://boinc.berkeley.edu/wiki/Client_configuration:

<zero_debts>
Set resource scheduling debts to zero. This lets you fix situations where client bugs have resulted in distorted debt values. Set it, run the client, then clear it (otherwise you'll start out with zero debts every time you run the client). New in 6.6.11

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.

---

BOINC blog

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.

Here you have the Changelog 6.6.11 ;)

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)

and

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

Sounds good, I'll give it a try.

/edit/

Another quote:

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