The following fixes are included in this BOINC client software version released earlier today for testing...

Mac client: fix bug in build script so that curl-7.19.2 actually

does build with c-ares 1.6.0. Fixes #830. (Checked into

boinc_core_release_6_6_2 tag and boinc_core_release_6_6a branch.)

- client: fix messages

- client: fetch work from non-CPU-intensive projects

- client: compile fix, remove spurious message

- MGR: Make sure the UI thread doesn't call a GUI RPC

that uses the SET_LOCALE class.

- MGR: fix compile error.

- client: if an app has avg_ncpus < 1, run it at above-idle priority

even if it doesn't use a coprocessor.

- scheduler: added an "nci" (non CPU intensive) plan class

to sched_plan.cpp. It declares the use of 1% of a CPU.



The above two changes are intended to allow the QCN app to

run at above_idle priority, which it needs in order to do 500Hz polling.



- API: the std::string version of boinc_resolve_filename()

acts the same as the char[] version.

- client sandbox: add details in switcher_exec "execv failed" message.

- MGR: Work around bug in generic list control GetSelectedItemCount()

which caused incorrect update of buttons in Projects tab after

detching from a project; remove redundant UpdateSelection() call.

- MGR: Remove override of GetSelectedItemCount() introduced yesterday;

instead, call DeleteItem() rather than SetItemCount() when number of

rows has been reduced, to allow virtual ListCtrl adjust its list of

selected rows (and thus keep its count in sync with reality.)

- MGR: Don't use wxT() to describe parameters passed to GUI RPCs.

- MGR: In CBOINCClientManager::StartupBOINCCore() allow time for Client

to start up, to avoid repeated attempts which put spurious messages

"Another instance Another instance of BOINC is running" in

stderrdae.txt.

- client: simplify message describing scheduler request;

to get work request details, use <sched_op_debug>

- client: when preempting a process, remove it from memory if:

1) it uses a coprocessor

2) it has checkpointed since the client started

3) it's being preempted because of a user action

(suspend job, project, or all processing)

or user preference (time of day, computer in use)

- client: clear debts when reset project

- client: respect work-fetch backoff for non-CPU-intensive projects

- client: for non-CPU-intensive project, fetch new job

if no currently running jobs

- client: skip non-CPU-intensive projects in debt calculations

- manager: show resource backoff times correctly

- client: if we're doing an RPC (for whatever reason)

to a non-CPU-intensive project without a job, ask for one.

- client: change the LTD policy so that

1) net adjustment for eligible projects is zero;

2) max LTD is zero

---

Crunching for the benefit of humanity and in memory of my dad and other family members.

Has anyone tired it?

Has anyone tired it?

http://www.gpugrid.net/forum_thread.php?id=684&nowrap=true#6154

Just installed it on Vista x64 + 2x 8800GS--It aborted all current tasks (WCG and GPUGrid) and re-DLed new ones. Currently it has only DLed 2x GPUGrid WUs--it has always been 4x WUs in every previous version. Cpu usage is 0-2%.

Time to Completion is ~ 1hr 13mins....I doubt that is correct, but that's what it's showing for both WUs. Time to Completion is steadily ticking upward, but Cpu usage moves up 1sec for evey ~23secs of realtime.


It's only been installed for ~10mins, so we'll see how it goes....


Manual update retrieves no new WUs on WCG or GPUGrid. I should have a larger cache on both projects, but things are running atm.

Updated driver from 180.48 to 181.22....no noticeable difference....

I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work.

N

---

Crunching for the benefit of humanity and in memory of my dad and other family members.

Yesterday I upgraded BOINC 6.4.5 to 6.6.3 without any problems on an Intel Quad Q6600 with WinXP SP3.
Although it requests very often new work units, it doesn't get too much work (in contrast to a BOINC 6.2.2 install I had tried before).

I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work.

N

Agreed, Mine has picked up 2 more WUs since my last post. Cpu usage is still the same 0-2%. So far everything seems good, except losing all of the work and WUs during the change-over....

Just installed 6.6.3 into another rig. It did not abort the WUs, etc. Started up, benchmarked and went to work--NP. But this machine is coming from 6.3.21, so I would say that's the difference.

The other rig was updated from 6.4.5.

Edit: Cpu usage is high on this rig....~25%, but I am willing to assume atm that it's because of the older WUs.

So far everything seems good, except losing all of the work and WUs during the change-over....

I upgraded about 6 hours ago on both machines with no problems so far.

I've had problems with the installer not stopping the GPU task cleanly in the past so I suspended all activity before running the installer. I let the installer shut down the boinc client and the boinc manager though. I didn't loose any work units doing it that way, but then I am using the Win 32 bit variant and you are on the Win 64 bit.

Phoneman1

So far everything seems good, except losing all of the work and WUs during the change-over....

I upgraded about 6 hours ago on both machines with no problems so far.

I've had problems with the installer not stopping the GPU task cleanly in the past so I suspended all activity before running the installer. I let the installer shut down the boinc client and the boinc manager though. I didn't loose any work units doing it that way, but then I am using the Win 32 bit variant and you are on the Win 64 bit.

Phoneman1

I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21.

Going into 6.4.? I lost all WUs and coming out of it--same thing.

It can't seem to download any WU.

---

I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21.

Going into 6.4.? I lost all WUs and coming out of it--same thing.

Interesting, I wonder why this is happening to you? I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project.

I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project.

The loss of GPUgrid Wu's has been a hit or miss thing with many people. It depends on OS, Client, how you shutdown the client, upgrading or downgrading etc. Many have not been 'Bit' by this, some have... I try to suspend "non-running" Wu's and run down my "Active Wu's" just in case, then upgrade. I hate losing 'half crunched' Wu's....in the name of science...

---

Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.

Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?!

---

From Siberia with love!

Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?!

Well, the good news is that there was only one major bug in 6.6.3 in calculating LTD ... which may very well mean that you will have trouble getting work ... :)

were it me, I would down level again until 6.6.4 ...

Has anyone tired it?

Yes, I tired... Tired of waiting for NORMAL version of BOINC, which could automatically get work for gpugrid (CUDA s@h, CUDA e@h in future)... :-)

---

From Siberia with love!

I couldn't get any new work GPU units on 2 different Box's using 6.6.3 ...

The 6.6.3 is running fine , but there are some changes I don't like. I can't see the amount of called work and had on one PC the situation, that he crunched all WUs and would not call new work 'til the last WU had less than 2 hours to work.

I don't like it, if the BM works like a black box and I get no information. I've described this on the Boinc dev forum

---

Well, the good news is that there was only one major bug in 6.6.3 in calculating LTD ... which may very well mean that you will have trouble getting work ... :)

According to Boincview GPU's LTD is now zero on both of my machines. My other project, Cosmology, shows -4.8 million on one and -11.2 million on the other.

It does not seem to have afftected getting work for either project. On both machines 1 GPU is running and 2 are queued ready. Three of those queued were downloaded today, I upgraded to 6.6.3 this time yesterday.

There are 4 Cosmology tasks running on each machine and the normal number (half a day's worth) queued ready to run.

I'm going to stop Boinc and reset all the LTDs to zero and see what happens.

I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects.

Phoneman1

I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects.

Phoneman1

Yes, that is the intent. Also making minor changes for non-CPU projects ...

If you are attached to lots of projects JM VII found issues that indicate that you can run dry of work with 6.6.3 ... YMMV