Currently there should be no major *known* bugs. We should cover Win64 and Linux, with reasonably recent cards.

Unfortunately, an internal cleanup in the filenames will make *existing* WUs fail. Sorry about that. Will send new test WUs soon.

By the way, the scheduler for this app will base its decision simply on the CUDA version supported by your driver, rather than other heuristics.

Yes, I have had several task failures today when I never had any. Validated three test tasks with the new 2.10 app and one normal task.

The DHFR210 set was botched because old versions were still lurking around. I deprecated all the old apps now. The 210a set was created after this so should be ok.

CUDA version supported by your driver, rather than other heuristics

Which version is recommended as the minimum now?

MrS

---

Scanning for our furry friends since Jan 2002

Looking at the supported applications page - http://www.gpugrid.net/apps.php

Supported "New version of ACEMD" applications:
Linux - GPU/driver capable of CUDA80 or better
Windows - GPU/driver capable of CUDA92 or better

Which version is recommended as the minimum now?

As per Nvidia deployment documentation (previously posted by Keith Myers): https://docs.nvidia.com/deploy/cuda-compatibility/index.html

CUDA80 Minimum Driver r367.48 or higher
CUDA92 Minimum Driver r396.26 or higher
CUDA100 Minimum Driver r410.48 or higher
CUDA101 Minimum Driver r418.39 or higher

More failures because the old app (206) is still being sent out despite being deprecated.

Which version is recommended as the minimum now?

CUDA80 Minimum Driver r367.48 or higher
CUDA92 Minimum Driver r396.26 or higher
CUDA100 Minimum Driver r410.48 or higher
CUDA101 Minimum Driver r418.39 or higher

Exactly. Updated drivers are necessary for RTX users. They should go for r418.39 or higher.

Seems to be working. I added a FAQ item. Old WUs may still fail.

It also depends on what generation of card you have. My GTX 980 with the 430.26 drivers running under Ubuntu 18.04 is getting the CUDA 100 work units. It ran a total time of 43 minutes for a a81-TONI_TESTTESTLONG210. But it uses a whole CPU core, so I just reserve one for it.

I will await the real work units before doing more.

Now we need 10,000 WUs loaded.

---

Now we need 10,000 WUs loaded.

+1

Over the past several days I have received 4 ACEMD 210 WU's on two Linux machines with 3 GTX-1060's and all validated fine (3 x 7,500 and 1 x 75,000 points). Linux machines awaiting production WU's anytime.

Could you please answer these 2 questions...
... and consider including their answers in the FAQ thread here:
http://www.gpugrid.net/forum_thread.php?id=5002

2 questions:

1) Is the new app capable of resuming on a different GPU? I ask, because my main 2 crunching PCs are below, each having 3 different GPU types, and you said "no major known bugs", but I thought I saw some other report saying earlier how resuming on a different GPU type wasn't working yet.

2) Will this app work for my GTX 660 Ti that is in the same PC as newer generation GPUs? I believe mixing Maxwell and Pascal was a problem previously, which is why I'm asking about your new app.

Depending on your answers, both of these would be major problems for me, as I'm trying to keep these PCs stable while also working long-running RNA World tasks.

Please let me know,
Thanks,
Jacob Klein

PC 1: RTX 2080, GTX 980 Ti, GTX 980
PC 2: GTX 1050 Ti, GTX 970, GTX 660 Ti

As far as I know, you still can't resume a task on a different card type. I solved it by changing my preferences to switch among apps to 360 minutes vice the default 60 minutes and that solves the issue. The task starts and finishes on the same card. Haven't seen any task require that long to finish yet but probably will be adequate until we get the app declared to Main and start getting Long tasks again with the new apps.

If you have the same card type in a multiple card host, there is no issue starting on one card and finishing on another.

Sadly, one still can't restart between on different card types.

Regarding the mixing of cards: I don't see why it shouldn't work, but a real world test will confirm.

Could you please answer these 2 questions...
... and consider including their answers in the FAQ thread here:
http://www.gpugrid.net/forum_thread.php?id=5002

2 questions:

1) Is the new app capable of resuming on a different GPU? I ask, because my main 2 crunching PCs are below, each having 3 different GPU types, and you said "no major known bugs", but I thought I saw some other report saying earlier how resuming on a different GPU type wasn't working yet.

2) Will this app work for my GTX 660 Ti that is in the same PC as newer generation GPUs? I believe mixing Maxwell and Pascal was a problem previously, which is why I'm asking about your new app.

Depending on your answers, both of these would be major problems for me, as I'm trying to keep these PCs stable while also working long-running RNA World tasks.

Please let me know,
Thanks,
Jacob Klein

PC 1: RTX 2080, GTX 980 Ti, GTX 980
PC 2: GTX 1050 Ti, GTX 970, GTX 660 Ti

Are there any plans to allow the app to resume on a different GPU?

We looked into it, but do not know if and when there will be progress on the front. For the time being, I've amended the FAQ with a pointer on gpu exclusion.

Thank you. That is suitable, and I plan on implementing that approach shortly for one of my systems that gets suspended/resumed a lot. Did you know I'm responsible for exclude_gpu existing? ;)

Thank you. That is suitable, and I plan on implementing that approach shortly for one of my systems that gets suspended/resumed a lot. Did you know I'm responsible for exclude_gpu existing? ;)

No I didn't and let me add: well done :)