Is it just me or is the cuda 4.2 WUs 30-40 percent faster than the 3.1s are.
It seems amazing the difference is so extreme.

Also, is it a good time now to get a 680 ? now that the project will support it ??

Is it just me or is the cuda 4.2 WUs 30-40 percent faster than the 3.1s are.

It's much faster on every host.

It seems amazing the difference is so extreme.

It is amazing, but it will vary among different wourkunits.

Also, is it a good time now to get a 680 ? now that the project will support it ??

Definitely!

every host? i still get app 3.1 wus on the 285gtx O.o is it because cc1.3? or must i reattach?

on the 560ti i got 4.2 and i was supprised it done a short WU in 4 hours (before i think it was 5,5h?), so nice speed there ^^

---

DSKAG Austria Research Team: http://www.research.dskag.at

The improvement is very noticeable on the normal length tasks, and certainly more than the expected 15% improvement. However it does vary considerably, from task to task!
I'll quote myself from here:

BTW the performance improvement I'm seeing on my CC2.0 Fermi between running tasks on the CUDA4.2 and CUDA3.1 app varies from ~23% to ~56%

IBUCH_3_affTRYP ~23% faster
PAOLA_3EKO ~36% faster
MJHARVEY_MJHXA1 ~56% faster

Different setups will have somewhat different performance improvements; GPU type/spec, CPU type (performance), free CPU count, RAM type... The more the app is optimized the greater the impact of the performance from other resources; the greater the potential for bottlenecks.

I expect similar improvements for the long app when it arrives.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Hi: All tasks are downloaded 4.2 CUDA GTX295 mistake on my Ubuntu 12.04-64bit driver 295.59 the CUDA 3.1 are working perfectly.

process exited with code 247 (0xf7, -9)

This might result from a missing/incompatible Library file. Check if there are any updates.

Is anyone else having this problem?

I know there are a few people with Kernal/driver mismatches:

process exited with code 255 (0xff, -1)
</message>
<stderr_txt>
Error: API mismatch: the NVIDIA kernel module has version 295.40,
but this NVIDIA driver component has version 295.53. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.

Perhaps there is a general problem with CC1.3 cards and the 4.2app on Linux?

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Or a problem in some Linux driver packages?

MrS

---

Scanning for our furry friends since Jan 2002

Switched to cuda4.2 units for today.... so far 2 completed units and 3 have failed exit code - 98 (0x62)

If you updated the driver after starting a task, that task will probably fail.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

If you updated the driver after starting a task, that task will probably fail.

Been running the updated driver for a couple of weeks and 3.1 tasks (long) have been running ok.

Now had 6 failures and 2 completed.

My crunchers will be going offline whilst I jet off for a family holiday. Will see how things run when I get back.

Now had 6 failures and 2 completed.

The CUDA4.2 failures could be caused by overclocking adjusted for CUDA3.1 tasks.
My GTX 480s need 25mV more for crunching CUDA4.2 tasks without failures, also my GTX 590s had to be set to 625MHz instead of 725MHz (I don't want to raise their voltage).

Hi, I reinstalled the Nvidia 295.59 driver without problem, the OS works perfectly and the GTX295 is two tasks normally CUDA 3.1.ACEMD2

We'll see if any task more CUDA 4.2.

Now had 6 failures and 2 completed.

The CUDA4.2 failures could be caused by overclocking adjusted for CUDA3.1 tasks.
My GTX 480s need 25mV more for crunching CUDA4.2 tasks without failures, also my GTX 590s had to be set to 625MHz instead of 725MHz (I don't want to raise their voltage).

Will try fiddling around with settings when I return from holiday.

If the long queue is switching to CUDA4.2 I'll try and get the cruncher stable on shorties first.

The problems can wait. Enjoy your holiday ;)

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

I still have errors in CUDA 4.2, Nvidia driver 302.17 installed new, not GTX295 OC.

CUDA 3.1 is working perfectly

Error: "process exited with code 247 (0xf7, -9)"

i am here with XP and 301.42, still getting errors with 2x 460 GTX.

Now its some new on cuda 4.2 PAOLA, a bluescreen, tell that:

nv4_disp

0x000000EA
0x89788770
0x89FC06C8
0xB84DBCBC
0x00000001

Could that say someting !?

Edit:

ok, raised the voltage by 25mV, now waiting and watching.

ok 30 minutes , and no error. yeepee !!!

No one answered me for some days now, hope it was only a overreading ^^ Are the cuda 42 apps only for fermi&kepler, because i get only cuda31 apps (yes i tested short WUs) on my 285gtx or must i reattach this machine? (what i must time right because its a unattended machine)

---

DSKAG Austria Research Team: http://www.research.dskag.at

You're running driver: 301.42, so this shouldn't be an issue. Maybe you selected one the queue which doesn't have the new app yet?

MrS

---

Scanning for our furry friends since Jan 2002

4.2 CUDA tasks keep getting error on my GTX295 Linux.

Can anyone confirm if they only work the FERMI and KEPLER ... is to avoid wasting time, yours and mine. Thank you.

I tried both long and short. So this shouldnt the problem. But ok it seems there are still some probs with cuda 42 apps when i read the threads and i need valid results not wasting time :) only wanted to try one if it works or not as info for the team.

---

DSKAG Austria Research Team: http://www.research.dskag.at