GDF

Hmmm...a man of few words.

Since it's posted, it must be safe...

---

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

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

It is also out for Linux, x86 and 64.

Wow, that looks a lot better than 6.3.14 and the 32bit 6.3.18 to me...
Now without setting cpus or needing to suspend most tasks, it runs 2+1 tasks on a Dualcore with 1 GPU...
I suspended the units, restarted the client etc, it keeps the same number running

Much better now :)

Well it seems to be working better. 4 CPU tasks plus 1 CUDA.

However it did something odd when I first started....it says it generated a new CPID for the PC and trashed the old CUDA WU's in the cache. The WU status briefly changed to "Cancelled by Project" or something similar and then it downloaded a new set of CUDA WU's.

The box is this one: http://www.gpugrid.net/show_host_detail.php?hostid=10619

It shows 3 client aborted WU's, followed by 4 new ones. I've never seen that behaviour before when upgrading a version of Boinc. However, it does seem to be running correctly.

---

I don't see any difference from 6.3.17. Runs fine on Win64 (so far...). I have been running 6.3.17 fine with 2+1 running, without making any changes in client settings.

2 cpu + 1 gpu task on an AMD X2, just like 6.3.17.

With the GPU using 16% of cpu cycles, just like 6.3.17.

I did not lose any GPU tasks (1 running, 1 ready to run) after the upgrade.

---

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

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

Now the 2nd box is upgraded and this time no lost WU's. Odd....

Not to worry: it looks good with no pre-empted (waiting) Cuda or CPU WU's so far

---

Switched from 6.3.17 to 6.3.19, no WU crashes or anything.

EDIT: running 5 tasks now, so you can probably forget about my comment below.

But something curious: it resumed all 4 QMC CPU tasks and the one GPU task. But after 8s of CPU time for one CPU task it stopped. There is no message about this in BOINC, however. It says "running 4 tasks" and shows the one in question as "waiting to run". Overall CPU utilization is 95-96%, whereas it had been 100% with 5 tasks running.

I suspended QMC manually and there was no message about this either. All 4 tasks resumed, but the 4th one got stopped within seconds again.

MrS

---

Scanning for our furry friends since Jan 2002

Installed on 5 Box's with no Problems or lost Wus, upon startup all 5 Box's showed 5 Wu's running with a CUDA Wu being 1 of them. But now after 10-15 Minutes only 1 Box still shows 5 Wu's runnning with the other4 showing 4 Wu's running with a CUDA Wu being 1 of them ...

Installed on 6 machines now: across Linux, Vista32 and XP32. Only the first box had a strange event loosing some WU's on re-start, all others were ok.

I have the same symptoms as reported by ETA and PoorBoy - occasional switching of a CPU task to waiting, but it seems to settle down after a while. The Cuda task seems unaffected.

---

I did two windows x86 installs. I only had a few minutes to observe them though as it was the end of the work day.

One seemed to be fine running max of 2 cpus + 1 cuda.

The other did too, but within a minute it was not. I quit it, checked all config and preferences files, all looked ok with nothing to cause that. I turned on some debug flags and restarted it, it ran fine while watching it a few minutes. scratched head. then turned of debug as I did not want to leave it on all night and within 1 minute it was only running 1 cpu + 1 cuda. It is not perfect.

I don't have time to fully debug right now, next day or so or maybe the weekend.

However on quick test I was not able to get some of the bad errors that were in 6.3.16 or 6.3.17 so maybe those are gone.

I've installed 2 on Vista 64, one on XP 64. ALl are starting with 5 tasks (4+1). When I stop the running projekt and restart them, only 4 tasks are running (3+1). After a while 5 tasks are running again. Then I shorten the switch time between the application (Preferences, switch time between the application) and I could watch a strange behavior. 4 tasks running, 5 tasks running, 4 tasks running, can't find a system behind this.

---

Finding the same scenario everyone else is with sometimes 4 total tasks running and sometimes 5 but the gpu always runs now...no more stalls so that is good. I decided to just go with the 5 ncpus solution for now until its fixed. At least I will get maximum utilization that way ;)

running fine here on server 2008 x64. The lag in the eye-candy animations is greatly reduced, which is nice.

I think I found out why it was smother, the GPU app was taking up less than 1% of the CPU. I set it to realtime priority and its now 20% of 4 cores.

Wow, that looks a lot better than 6.3.14 and the 32bit 6.3.18 to me...
Now without setting cpus or needing to suspend most tasks, it runs 2+1 tasks on a Dualcore with 1 GPU...
I suspended the units, restarted the client etc, it keeps the same number running

Much better now :)

Now that I check my computer again after 14 hours passed, I find only 1+1 tasks running. After restarting the client, 2+1 are running again, I spend some time reading this thread and when I checked back, the second CPU tasks was "waiting to run" again. No entry to the log for that...

I'll try ncpus+1, if it then suspends one I'll not complain to much ;-)
The most important thing - keeping the GPU busy - is achieved :)

My quad is running 3 CPU + 1 CUDA. I have no ncpus set. Should it be lie this? Or should it be 4+1? I think this is set on the project side, right?

---

Reno, NV
Team: SETI.USA

6.3.17 sometimes also processed only 2 tasks, CPU+GPU WUs. I'll take a look at 6.3.19 now and compare.

God damn it! Again I see only 2 tastks running, CPU+GPU... But it had honestly started 3 tasks. And after a while it became to process only 2 WUs...

OK, heres some good news. I may have captured the bug happening with some debug info. Below is part of the email I sent the developer team, along with the debug info. I hope with this they can figure it out. I had 7 debug flags set, so hopefully ever little change was recorded.

If everyone would just remain calm and patient, we will eventually get this worked out. Remember that this is all new to users and devlopers, it has only been in development part of this year, whereas boinc itself has over 4 years of development.

Host #1 still running fine, 2 CPU + 1 CUDA/CPU<1.

Host #2 which was not I discovered the CPU job after at least 2 hours was not running, even though it said it was. In windows task manager it showed 0 CPU usage, so for some reason I've not seen it was hung up.

I shut down client, set debug flags on and restarted, then left client alone, I think. It only resumed the 1 CPU job and 1 CUDA/CPU<1 at that time. **Wrong behavior*

A little while ago I looked over and it showed the screen running 1 CPU, 1 CUDA/CPU<1 and 1 CPU as waiting to run. Note several other users on PS3GRID forum report same, less than max CPU running along with the CUDA/CPU<1.

I saved all the debug info, only problem is I do not know how far back that occurred, but it has to be in there somewhere. Notice too the time shows 00:00:35, If I remember there other times this happened, it happened at that exact same time, around 34-35 seconds they go to waiting.

Attached is debug log, cc_config, global_pref, global_prefs_override, client_state screenshot of tasks and screenshot of resource shares. I hope this would be enough to figure this out. I'll look it over my self tonight when I get home, although I do not follow all the debug too well. Hope its not too much info. Oh and I remember to reduce the images to jpeg this time instead of large bitmaps.