A very strange thing is happening on my host.

I´m using BOINC 6.3.10 with default settings (no messing around with ncpu+1 or something like that)

After I uploaded a new WU for GPU Grid last night I found my PC crunching happily two CPU Seti units alongside one GPUgrid WU.... (Core2 Duo)

The WU will be finished in about 1h so I can give you the time per step / estimated completion time.



Cu KyleFL

Hi

Same thing here, I am not using ncpu+1

Boinc 6.3.10 - Vista64

Same here but only on 2 from 4 computers. Is there any reason for that ?

I am using Boinc 6.3.10

Hello,

I had the same behavior last evening. Suddenly boinc started an extra GPUGrid-WU additional to the running CPDN and EAH. It is an old WU which is crunched before as an extra task on my Dualcore. For information: before that a new WU was downloaded. Yesterday evening I stopped Boinc overnight and in the morning I started BOINC again.
Now this behavior I see. Boinc starts GPU-Grid as a third tasks and after a short while (I think on the first checkpoint) the GPU-Grid-WU is stopped. Of course the GPU-Grid has the highest STD of all projects and on "right" scheduling this WU has to run with first priority. After on hour BOINC started GPU-Grid again and stops immediately.

I show you the stdoudae:

03-Oct-2008 08:02:43 [climateprediction.net] [cpu_sched] Starting hadam3h_c_94s16_2000_2000_4_2(resume)
03-Oct-2008 08:02:43 [climateprediction.net] Restarting task hadam3h_c_94s16_2000_2000_4_2 using hadam3 version 601
03-Oct-2008 08:02:43 [Einstein@Home] [cpu_sched] Starting h1_0538.40_S5R4__186_S5R4a_3(resume)
03-Oct-2008 08:02:59 [Einstein@Home] Restarting task h1_0538.40_S5R4__186_S5R4a_3 using einstein_S5R4 version 604
03-Oct-2008 08:08:08 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:13:31 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:18:53 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:24:14 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:29:36 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:34:58 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:40:19 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:45:40 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:46:45 [climateprediction.net] [checkpoint_debug] result hadam3h_c_94s16_2000_2000_4_2 checkpointed
03-Oct-2008 08:50:59 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 08:56:16 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 09:01:30 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 09:06:40 [Einstein@Home] [checkpoint_debug] result h1_0538.40_S5R4__186_S5R4a_3 checkpointed
03-Oct-2008 09:06:40 [PS3GRID] [cpu_sched] Starting DVH9626-GPUTEST3-1-10-acemd_0(resume)
03-Oct-2008 09:06:40 [PS3GRID] Restarting task DVH9626-GPUTEST3-1-10-acemd_0 using acemd version 645
03-Oct-2008 09:06:40 [QMC@HOME] [cpu_sched] Starting four_bench14a_s22-ecp2-QZ.7586_0(resume)
03-Oct-2008 09:06:40 [QMC@HOME] Restarting task four_bench14a_s22-ecp2-QZ.7586_0 using Amolqc-preRC1 version 501
03-Oct-2008 09:06:40 [Einstein@Home] [cpu_sched] Preempting h1_0538.40_S5R4__186_S5R4a_3 (left in memory)
03-Oct-2008 09:06:44 [QMC@HOME] [checkpoint_debug] result four_bench14a_s22-ecp2-QZ.7586_0 checkpointed
03-Oct-2008 09:06:44 [PS3GRID] [cpu_sched] Preempting DVH9626-GPUTEST3-1-10-acemd_0 (left in memory)
03-Oct-2008 09:08:54 [QMC@HOME] [checkpoint_debug] result four_bench14a_s22-ecp2-QZ.7586_0 checkpointed
...
03-Oct-2008 09:53:55 [QMC@HOME] Computation for task four_bench14a_s22-ecp2-QZ.7586_0 finished
03-Oct-2008 09:53:55 [PS3GRID] [cpu_sched] Resuming DVH9626-GPUTEST3-1-10-acemd_0
03-Oct-2008 09:53:55 [PS3GRID] Resuming task DVH9626-GPUTEST3-1-10-acemd_0 using acemd version 645
03-Oct-2008 09:53:55 [climateprediction.net] [cpu_sched] Starting hadam3h_c_94s21_2000_2000_4_2(resume)
03-Oct-2008 09:53:55 [climateprediction.net] Restarting task hadam3h_c_94s21_2000_2000_4_2 using hadam3 version 601
03-Oct-2008 09:54:55 [PS3GRID] [cpu_sched] Preempting DVH9626-GPUTEST3-1-10-acemd_0 (left in memory)

CPDN is still running, EAH is preempted, QMC is started and PS3 is started and then... PS3 is stopped.

I´m running 6.3.10 with no additional settings. I never touched cc_config.xml

A restart of neither boinc nor the computer alters the behavior.

Same here, had running 6 tasks on both Quad running PS3Grid. Had reboot both machines, same effect. Have killed the ncpus-entry in the cc_config.xml and now running 5 tasks on both machines.

Something changed in the code? Looks like PS3Grid is now running like DepSpid in the past (http://depspid.net/).

Edit: First only my two 64 bit Vista PCs affected, after upload the calculaed WU on the PC of Cebion now also our 32 bit XP Quad affected.

---

Same behaviour on my computer.
And i saw that the CPU time on different computer have decrease.

Before this update, on my Server 2003-x64, the CPU time was on average 2400 seconds, and for one task this morning, i can see only 800 seconds! But an increase of the total running time from 49000 seconds to 53000 seconds.

I don't understand what happened, because there has been a server upgrade last night, as GDF said.

Jim PROFIT

Ok -- my GPU WU is now finished:
12h instead of 9h.

After it finished the GPU-WU, it startet the next one -- running it alongside 2CPU WUs.
But it seems, that the GPU-WU is preempted for ~1minute after calculating one step. It trepeats infinity. Calculating -- preempted -- calculating -- and so on...

I´ve stopped the CPU-WU (Seti) tasks for now until we have sorted out the problem. After that the GPU-WU seems to be back on full crunching-speed.





Cu KyleFL

In That case just set <ncpus> to cores-1 (so f.i. 3 for a quad core) that ensures that one core always is unused for the gpu tasks.

GDF said that now it was a server setting, if the extra core gets dedicated to the GPU project or is free for other projects. So it seems like they changed the server setting but kept the client the same (6.45). It's a trade-off between loosing some speed on the GPUs under win and giving people a bit more CPU crunching power.

Edit: on my machine the GPU stopped after BOINC switched to the new behaviour. I rebooted (unrelated), increased resource share from 30% to 66% (quad core), set the debts back to 0 but still only 4 CPU tasks were running. Then I suspended the CPU project and finally BOINC started the GPU task again.

MrS

---

Scanning for our furry friends since Jan 2002

In That case just set <ncpus> to cores-1 (so f.i. 3 for a quad core) that ensures that one core always is unused for the gpu tasks.

It's not working, the gpu stop calculating after few seconds, if I set 2 cores on a dualcore cpu, three wu are calculating but after few seconds, the GPU stop calculating

Please GDF, do something to stop that, the time of calculation increase a lot :(

Could you repeat what I did (previous post) to make my GPU run again? Maybe it helps.

MrS

---

Scanning for our furry friends since Jan 2002

Surely this will help, but the balancing with the resourceshare is blown away by this method.

I think there must be a solution from the "chefs". ;-)

Setting Boinc to use only "50% of Prozessors" (DualCore) seems to work.

Boinc still seems to be using both cores (one for GPU - one for CPU) and not putting both tasks on one core.

That should do the trick for now.
Update: I roughly calculated the crunching time and the GPU-WU seems to be on full force like it was before.


But the question is: What had happend to change the behavior of Boinc?


Cu KyleFL

Could you repeat what I did (previous post) to make my GPU run again? Maybe it helps.

MrS

Thanks, it works fine with ncpu-1

just encountered it myself! No changes suddenly 4 wus + grid running.

Changed to ncpus=3 worked

I had too this morning 2 cpu + 1 GPU WUs running in Core 2 Duo and 4 cpu + 1 GPU in Quad core. But I have experienced a 20% download in my points per day, so I have put 50% and 75 % CPU use restriction respectively and now, as before, all is OK.

Back from work now, and after my early morning post in the other thread, I checked my boxes again.

They were running the same as this morning. So, I've just updated them all with a cc_config.xml file, setting ncpus-1 (ncpus=1 for dual core and ncpus=3 for quad) and have the same experience as other users: everything returns to normal.

Strange behaviour indeed??!

---

Back from work now, and after my early morning post in the other thread, I checked my boxes again.

They were running the same as this morning. So, I've just updated them all with a cc_config.xml file, setting ncpus-1 (ncpus=1 for dual core and ncpus=3 for quad) and have the same experience as other users: everything returns to normal.

Strange behaviour indeed??!

You don´t need to make this change through the cc_config.xml file. Just go into the settings and on the CPU-Tab:

On Multiprozessor Systems use only (50% on Core2Duo - 75% on Core2Quad - instead of the original 100%) of the prozessors.

That works the same way and is easier to change.


Cu KyleFL

BOINC seems to be completely out of shape. After finish the last WU I had again running 5 tasks on my Quad, but all are non-GPU-tasks. I had to stop BOINC and restart it, then are 4 CPU-tasks and one GPU-task are running. Another team-mate has on XP 32 bit the problem, that without a cc_config.xml 6 tasks are running. Nothing helps.

---

You don´t need to make this change through the cc_config.xml file. Just go into the settings and on the CPU-Tab:

But not if you have this entry in the cc_config.xml, then you have to chenge it or delete the file and restart BOINC.

---