It was not a bug, it was fix to a bug as some linux users would hang the workunits.

gdf

Application 6.12 cuda2.2 for linux and windows are now out.

gdf

How to disable recieving standard tasks that aren§t friendly to GTX260 65nm rev.A2 and get beta tasks only?
A few month ago it could be set, now I do not how to do it.

The are no unfriendly tasks. Beta work is only on for a few days before any release anyway.

gdf

How to disable recieving standard tasks that aren§t friendly to GTX260 65nm rev.A2 and get beta tasks only?
A few month ago it could be set, now I do not how to do it.

Application 6.12 cuda2.2 for linux and windows are now out.

gdf

The first 6.12 app I received preempted the 6.05 task on the machine. The 6.05 task suspended at 98% completion. Luckily I caught it and susprnded the 6.12 app. Something to fix on future app releases though...

Application 6.12 cuda2.2 for linux and windows are now out.

gdf

The first 6.12 app I received preempted the 6.05 task on the machine. The 6.05 task suspended at 98% completion. Luckily I caught it and susprnded the 6.12 app. Something to fix on future app releases though...

I've just had a v6.11 task preempt a v6.11 task......

BOINC thinks that the second task (newly downloaded) is going to miss deadline and needs High Priority, even though the estimated runtime (23 hours 48 minutes) and deadline (8 November) look normal for the machine.

I'm in the process of preparing logs and a screenshot for submitting to BOINC for analysis - I'll let you know what I get back.

sorry for off-topic, but:
right now i've got GTX275 running on 195.30 driver cudatoolkit 2.3 (linux). should I downgrade to 190.38 driver cudatoolkit 2.2? which one is faster - 2.3 or 2.2?

---

it's fine what you have.it should be the same speed.
gdf

sorry for off-topic, but:
right now i've got GTX275 running on 195.30 driver cudatoolkit 2.3 (linux). should I downgrade to 190.38 driver cudatoolkit 2.2? which one is faster - 2.3 or 2.2?

it's fine what you have.it should be the same speed.
gdf

thanks a lot :-)

---

Due to the fact that cuda3.2 is still immature, we are coming out with the new application for cuda3.1 instead.
Tomorrow beta units.

gdf

first WU (IBUCH) on 6.12 app finished. I'm running it on GTX275, 195.30 driver cudatoolkit 2.3 (linux). GPUGRID got dedicated core and runs with nice -10

1. looks it's 8-9% faster then the same WU on 6.04 app. That's amaizing :-)
2. it uses up to 20% of the core. that's awesome :-) looks I can use that core with nice 0 for CPU crunching.

the only thing - BOINC do not want to get or the project not sending the 2nd WU at all. and basically it starts to download new WU only when it finish to crunch. this means somewhat couple of minutes of idling.

---

Version 6.12 is causing my work unit to run HUGELY slower than previously, when I was using version 6.04. At version 6.04, I was able to complete a work unit every 1 1/2 days, and get the 25% bonus. Now under 6.12, I have one work unit that has run 13 hours and is 9.328% done, so it is estimated to take 140 hours or 5.8 days to complete. That is almost FOUR TIMES slower. Now, forget about trying to get the bonus, I might not even make the deadline. I'm using Ubuntu Linux with a GT220. I also notice that 6.04 was using lots of CPU power, and 6.12 is not.

ACEMDbeta 6.37 cuda3.1 for windows and linux are now available.
As usual you need to accept beta units.

gdf

All units that I get now are ok, but strange to me is that new app 6.11 uses 50% of my dual core CPU, and I see 25%-50% slowdown on my CPU projects. Anyone else experience this?

---

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

Version 6.12 is causing my work unit to run HUGELY slower than previously, when I was using version 6.04. At version 6.04, I was able to complete a work unit every 1 1/2 days, and get the 25% bonus. Now under 6.12, I have one work unit that has run 13 hours and is 9.328% done, so it is estimated to take 140 hours or 5.8 days to complete. That is almost FOUR TIMES slower. Now, forget about trying to get the bonus, I might not even make the deadline. I'm using Ubuntu Linux with a GT220. I also notice that 6.04 was using lots of CPU power, and 6.12 is not.

In WinXP-64 so far 6.12 is running about 10% slower than 6.05 on my systems, not a step forward either. In addition the new IBUCH_x_TRYP WUs are taking about the same time as earlier 13k credit WUs but yield only 10k WUs, so a double net loss.

How is it going with the cuda3.1 beta versions?

gdf
PS: This thread is for the new applications.

I just got one of the 6.12, and it will not finish in time, it will perhaps finish before the second one is sent again but I'm not sure.
Strange side effect: the application of all former WUs suddenly became "Not in DB" instead of "ACEMD2: GPU molecular dynamics v6.04 (cuda)".

I did old WUs of the same kind in about 60Ksec, that's less than 17h, enough time to get it back in time.
Now I'm at 10% after 16:40h, that just ridiculous.

How can I get back the good application and get rid of the junk one?

Edith likes to ask:
Why is this number crunching thread in the hardware related part of the forum?

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Hi folks,

I just noticed that processing new tasks is a lot slower than it used to be. I'm running Linux using a GT240 and it typically took me 12 hours to complete a unit using acemd2 version 604. Now I am processing a new task using acemd2 version 612 and more than 6 hours have passed while I am not even at 20 percent. Another major change is the CPU usage. The old acemd2 executable used nearly 100 percent CPU time but the new one uses less than 5 percent. Does anyone know what changed is this new version ?

Thanks, Tom

OK, I agree that I did a double post, but why is the whole thread moved from the proper software part of the forum, "Number crunching" to this hardware part "Graphic Cards"? You wouldn't expect software talk here.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Re cuda3.1 beta versions,

i7-920, XP x86, Boinc 6.10.58, 2 x GTX470, 260.99:

04/11/2010 18:58:18 GPUGRID Scheduler request completed: got 0 new tasks
04/11/2010 18:58:18 GPUGRID Message from server: No work sent
04/11/2010 18:58:18 GPUGRID Message from server: No work is available for ACEMD beta version
04/11/2010 18:58:18 GPUGRID Message from server: Fermi-class GPU not supported by cuda2.2

- Just picking up normal (non-beta) work now.