@ Keith - 6.3.17

Now I have four CPU and one GPU task running again. But it's to late for me to set up the debug stuff and watch BOINC... ;) Will do that tomorrow...

---

pixelicious.at - my little photoblog

@GDF
Maybe you should wait until an official 6.3.17 linux is made, as the last one I see is 6.3.14 on the dl page. Maybe you should switch back to CPU=1 until one is released, unless you have one all linux users can download.

++

Since 0.9 CPU setting is active, my GPU stops crunching after restarting the client within few minutes.
We should wait for 6.3.17 to be available for Linux also, to enable the 0.9 CPU share/weight/whatever...

So far except for a very brief period all I've ever seen on my Box's is 4 Wu's running. On 1 there were 5 running for about 5 minutes & then that was it, 4 on that Box too ever since, running 6.3.17 on all 5 of my GPU CUDA capable Box's.

@ Keith - 6.3.17

Now I have four CPU and one GPU task running again. But it's to late for me to set up the debug stuff and watch BOINC... ;) Will do that tomorrow...

Is this on your windows vista host ?

So far except for a very brief period all I've ever seen on my Box's is 4 Wu's running. On 1 there were 5 running for about 5 minutes & then that was it, 4 on that Box too ever since, running 6.3.17 on all 5 of my GPU CUDA capable Box's.

Can you specify the mix of 4 and 5 ?

What type of boxes ? Since your computers are hidden I can't look it up.

Yup Keith, that's on the Vista Ultimate 64 bit box, with BOINC 6.3.17.

---

pixelicious.at - my little photoblog

hmm - i'm running fiesta x64u too (6.3.17) - 4 ABC-WUs and 1 Cuda - the only thing is that 1 of the ABC-tasks is suspending from time to time.

running XP32 SP3, was running fine, 4 3x+1 wu and 1 GPU with ncpu+1. I removed the ncpu+1, installed BOINC 5.3.17, restarted, let it go through a completed gpu wu, it's now running 3 3x+1 and 1 GPU grid wu

---

Team Starfire World BOINC
IRC- irc//irc.teamstarfire.net:6667/team_starfire

Do we need to wait for new work for this to take affect?

I am seeing "Running (1.00 CPUs, 1 CUDA)" on 6.3.17

Yes, any exsiting work you have will run at what ever it was sent at. You will notice the change was new work starts to download, although there may still be some work in the server queue at the old setting.

It is still on the same wu, but I have updated the project. I now see



With 4 cpu tasks running, 1 gpu task running (high priority). Unfortunately, taskman shows the GPU task running at the same priority as the CPU task, so is going to fight the cpu.

confirmed in my team, all three machines using 6.3.17:

working on two xp 32 bit machines as expected

NOT working on my vista 64 bit machine (instead 16-18% CPU, task gets only 1-2%, CPU Tasks get 24-25% each, slowdown as expected). Therefore im still using ncpus=4 till this is resolved.

With 4 cpu tasks running, 1 gpu task running (high priority). Unfortunately, taskman shows the GPU task running at the same priority as the CPU task, so is going to fight the cpu.

Well, the WU in question finished and a new one started. It is running the same (0.9 CPU, 1GPU) but the thread is running at NORMAL priority according to taskman. This is what was advertised and what I am seeing, so it looks good.

GPUGRID is now requesting less than one processor such that people can run a further cpu job.
This will stay if there are no problems. People should not use ncpus anymore and update to clients 6.3.17 or 6.3.14.

GDF

I would say use 6.3.17. So far no problems. I did extensive testing with 6.3.15 with no problems as far as job scheduling, testing both CPU=1 and CPU<1 jobs, which always ran and ran the proper number of other CPU only jobs. 6.3.17 should be the same as far as that goes.

6.3.14 will work some, but eventually it will leave no GPU tasks running, or only a GPU running. It does not behave well.

I had been running 6.3.14, but just moved to 6.3.17. My system is now crunching 2 WUs with .9 CPU 1 CUDA, and after the initial install of 6.3.17 was crunching 3 other CPU tasks. Now, after 1 hour or so, it is back to running on 2 CPU + 2 GPU tasks -- pretty much the same results with 6.3.14 before the .9 CPU 1 CUDA was turned on. I generally see the 2 CPU tasks running 25% each on my Q6600, with the 2 GPU tasks taking about 18% each -- leaving about 12% idle.

UPDATE: Once I closed BOINC manager and the boinc.exe process, reopening the BOINC manager once again restarted 3 CPU tasks + 2 GPU tasks. Within seconds, the extra CPU task went back to "Waiting to run" which is what happened before. Apparently, this is repeatable.

I have Boinc .14 that was running 5 tasks set by the ncpu flag.

After noticing the .9 CPU 1 cuda switch the project now runs 5 cpu tasks and 1 GPU.

I've deleted the cc_config file and now it runs 4 tasks plus 1 GPU.

The GPU consumes 2% to 5% of the CPU.

Already noticing the 30% performance increase, my daily 9500 credits jumped to the 13000s.

Bottom line, good work, although I'm hesitant to switch to boinc .17

Without admin rights only three task + ps3grid are running on a quad. With admin rigts there are 4 task + ps3grid running.

That is not correct! It was my mistake. I haven't enough time. All is working fine with normal user rights.

But! The most time only 3 Task and 1 cuda running in stet of 4 task and 1 cuda.

---

Constant dripping wears away the stone. :)

Klat,

I think I've seen the same behaviour as you did when I switched to 6.3.17 yesterday. BOINC manager showed 3 CPU + 1 GPU task running on my quad. However, there's a minor screen refresh issue where the manager shows a task as "ready to run" whereas in reality it's already started. I checked with task manager: 4 CPU and 1 GPU were running, although the 4th CPU task almost didn't get any CPU time, overall utilization was 93%.

After this night everything is running as expected, though. Didn't change anything. Now it's 4 CPU + 1 GPU, cpu utilization 100% and the GPU task taking between 9 and 22% (one core 25%). GPU temperature seems to be the same so I hope it's still running full throttle.

MrS

---

Scanning for our furry friends since Jan 2002

Already noticing the 30% performance increase, my daily 9500 credits jumped to the 13000s.

You mean your GPU-Grid credits jumped from ~9.500 per day to 13.000?

Well, that's not normally related to the "CPU request is now < 1" switch. You should have gotten the higher amount of credtis since the 6.48 client was released, but at the expense of sacrificing CPU time. If you are seeing the improved GPU times only now it means your GPUs were CPU-limited before and could not reach their potential due to the use of ncpus+1 (or 2 in your case). What helps you is probably the "normal" priority setting, which was introduced now.

Bottom line, good work, although I'm hesitant to switch to boinc .17

Why? (the answer may very well belong into the thread for 6.3.17)

MrS

---

Scanning for our furry friends since Jan 2002

Klat,

I think I've seen the same behaviour as you did when I switched to 6.3.17 yesterday. BOINC manager showed 3 CPU + 1 GPU task running on my quad. However, there's a minor screen refresh issue where the manager shows a task as "ready to run" whereas in reality it's already started. I checked with task manager: 4 CPU and 1 GPU were running, although the 4th CPU task almost didn't get any CPU time, overall utilization was 93%.

After this night everything is running as expected, though. Didn't change anything. Now it's 4 CPU + 1 GPU, cpu utilization 100% and the GPU task taking between 9 and 22% (one core 25%). GPU temperature seems to be the same so I hope it's still running full throttle.

MrS

Well, actually there's really something wrong with the scheduler. I noticed a few times that BOINC sometimes runs 3 CPU plus 1 GPU task, and sometimes 4 CPU plus 1 GPU task. I already reported this to BOINC alpha, but haven't got an answer until now...

---

pixelicious.at - my little photoblog

The problem could be related to what I posted in the 6.3.17 thread (resuming issue).

MrS

---

Scanning for our furry friends since Jan 2002

From the logs it looked like it has to do with the preemption of tasks, but I'm not a dev, I only report what I see... ;)

---

pixelicious.at - my little photoblog

Would like to report back that under Linux and 6.3.14 the gpu task did eventually start and run full time,but it was a different task as I aborted a few that would only run 30 secs every 30 min...since it is on a 9800GT it is only 75% complete and will report back what happens as it completes to start the next one.

Edit-Bad news...my other host running CUDA on Linux is exhibiting the same behaviour as in waiting to run.....4cpu's running gpu waiting :(...I hope they release a new client soon for Linux...