By beginning of next year, we would like to remove the cuda3.1 applications.
These are still the old apps and don't have several of the new features available in the new app which we need to do the science.

We will probably have a cuda4.2 app only, so within the next few months, drivers should be upgraded to at least this version. In our machines, the latest driver 304.51 works quite nicely under Linux, very robust.

gdf

Please do. Due to their inefficiency, the sooner the better, IMHO.

---

Pretty please, for the benefit of those of us who know not what CUDA 3.1 and CUDA 4.2 are, all we need to know is what BOINC and Nvidia drivers we should be using (I think...).

Also, it would be good to know well in advance when you plan to drop support for intermediate cards, e.g., my faithful GTX 460., which I bought just for GPUGRID when you put my GSO 9600 out to pasture.

ALSO - If Nathan is still with you, he who I assume is responsible for NATHAN WUs, can he please stop sending me WUs that totally clog my PC? If he wants to know which WUs, I have that information - I've been keeping a log...

The log tell me that, of the 30 NATHANs I've had these past three weeks, 50% I've aborted so I can get a few minutes of peaceful, quiet PC time, just for me, not for NATHAN!!

Thank you.

---

In the last hour I've aborted four NATHANs for killing my PC performance. This is getting ridiculous!!

---

nathan WU should have no difference from the others if not that they are large systems.
What is the problem exactly?


gdf

Pretty please, for the benefit of those of us who know not what CUDA 3.1 and CUDA 4.2 are, all we need to know is what BOINC and Nvidia drivers we should be using (I think...).

Also, it would be good to know well in advance when you plan to drop support for intermediate cards, e.g., my faithful GTX 460., which I bought just for GPUGRID when you put my GSO 9600 out to pasture.

Fermi cards can run CUDA 4.2 tasks. This includes the GTX 460.
Older cards (GeForce 200 series and below) may not be capable of running CUDA 4.3 and would not perform well.

---

FAQ's

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

Yes when 31 get killed we can all throgh out our 2xx cards :/ but im happy that you let them actived until today. Im sure i have a other project in reserve for the 285 gtx when you do the final change ^^ i think yo will inform us a week before change? Perhaps i have enough money to buy a new nvidia card then after christmas ^^

---

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

We might be able to keep the old application for cuda3.1, but at least one of the two queues must be with just the new app.

gdf

We might be able to keep the old application for cuda3.1, but at least one of the two queues must be with just the new app.

gdf

please make the long run queue only 4.2+

---

XtremeSystems.org - #1 Team in GPUGrid

We might be able to keep the old application for cuda3.1, but at least one of the two queues must be with just the new app.

gdf

please make the long run queue only 4.2+

I thought the original plan was to use cuda40 and cuda42. If we're going to keep cuda31 around then limit it to the short queue, with the beta and long queues using cuda42.

Is there any advantage to using cuda50 at this point or would it be too much development effort?

---

BOINC blog

for cuda5 there is no point, no speed advantage. The problem of cuda4.0 is that it seems buggy.
We could do cuda4.1 instead of cuda4.2, but there is little change.

gdf

For now could you place,
4.2 WU's into the Long queue only,
3.1 WU's into the short queue,
and if need be put shorter 4.2 WU's into the Beta queue?

---

FAQ's

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

nathan WU should have no difference from the others if not that they are large systems.
What is the problem exactly?gdf

Hello GDF. I shall be delighted to tell you EXACTLY what the problems are despite the fact that they have produced no solutions in
this thread.

I can tell you EXACTLY which NATANs kill my PC performance, and which don't.

If you're listening, I'm ready...

Tom

---

You only have 6GB of memory with Windows 7 no less, it's amazing you can run any GPU wu's at all. You're getting alot of reads and writes to you're scratch file, that would make it diffacult for any computer to respond quickly. Anyway, just a thought with RAM so cheap these days.

6GB is normally enough - even for W7.
If tomba was running 8 Rosetta tasks then it might be an issue as those tasks can use 400BM RAM, so 3GB of RAM could be being used. More importantly, the CPU could be being saturated. W7 typically uses around 2GB RAM. Of course other RAM heavy apps (including browsers) could be an issue too, but tomba's problem is specific to one type of GPUGrid WU.
Anyway, none of this has anything to do with this thread, 'CUDA upgrade notice'.

---

FAQ's

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

You only have 6GB of memory with Windows 7 no less, it's amazing you can run any GPU wu's at all. You're getting alot of reads and writes to you're scratch file, that would make it diffacult for any computer to respond quickly. Anyway, just a thought with RAM so cheap these days.

Lol then i must have massive problems on my 2gb ram machine with win7 ;) *ironic* 6gb is way enough O.o

---

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

Anyway, none of this has anything to do with this thread, 'CUDA upgrade notice'.

You're absolutely right and I apologize, but I figured that this thread was started by someone on the development team who might, perhaps, bring my problem to the attention of their colleague who does NATHANs...

---

I got a big problem. I can't complete any task on my computer.
I use asus GTS 450 with NVIDIA DRIVERS 301.42WHQL 、 intel E5200 、 4G DDRII (PC3200)、Windows 7 Enterprise (x64) and BOINC 7.0.28(x64).

but...
It's seems too bad >.<

[/code]

I updated drivers for my GTX 260 yesterday, and cuda42 work units apparently started crashing.

Last 3 tasks (standard queue):
* 6044359 - ACEMD2: GPU molecular dynamics v6.16 (cuda42) - CRASHED
* 6047209 - ACEMD2: GPU molecular dynamics v6.16 (cuda31) - success
* 6048860 - ACEMD2: GPU molecular dynamics v6.16 (cuda42) - CRASHED

I had no problem prior to the update. (http://www.gpugrid.net/results.php?userid=81842). Indeed task 6044359 was running fine, then crashed immediately after restarting BOINC, following the driver update.

NB: The driver (306.97 WHQL) arrived via Windows Update yesterday. Prior to that, I was running the last version Windows Update sent me (295.73 I think, possibly 296.10). I wonder if others have starting seeing similar issues now that WU has pushed this driver?

GTX 260, Win7-x64, BOINC 7.0.28(x64), Intel i7-860

yes because the 2xx series (i wrote too in this thread) is not good for cuda42..so get your driver back down in 2xx Range. Run it until end of the year and when it changes switch fully to short WUs where it seems perhaps to continue with 31 when i read the thread correct. Or buy a new card for gpugrid. The only chance is to downclock core (-50Mhz?) and memory (-100Mhz) from the graphiccard and look if it perhaps helps. but this tip is more for some fermi cards (like my 560TI) who produce cuda42 errors from time to time too.

---

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