It's been over a month since our last update, but I now have some good news. I have made some improvements to the GPU code and am ready to start deploying the new GPU apps.

I will start with the AMD OpenCL version for Linux. This will be a beta version. I have had a hell of a time with the AMD implementation of openCL, and this app still doesn't work on my Fedora system, and I believe strongly it's due to the graphics driver. But I have had the help of a volunteer named Wiktor and it runs fine for him (I believe he runs Ubuntu). Please keep in mind that AMD officially only supports RHEL and Ubuntu, so I will be interested to hear if this app works for anyone with an "unsupported" linux distro like myself.

I also have openCL Windows apps that were cross compiled using mingW. I have no means of testing these, so I am not ready to deploy them just yet. But if anyone would like to take them for a spin offline, please let me know, and I can send them to you.

How about writing the AMD GPU app so it works with the ROCm opencl driver. The ROCm driver works great for Einstein@home.

How about writing the AMD GPU app so it works with the ROCm opencl driver. The ROCm driver works great for Einstein@home.

As far as I know, it has nothing to do with the app. The openCL code works perfectly on Nvidia and with AMD on Ubuntu. I think what you are suggesting is I try the ROCm driver on my Fedora system. I did try that early on with no success, but perhaps I should try again now that I have more experience with video drivers.

Feel free to send me the openCL Windows app via mail. Would like to give it a try. :)

How about writing the AMD GPU app so it works with the ROCm opencl driver. The ROCm driver works great for Einstein@home.

As far as I know, it has nothing to do with the app. The openCL code works perfectly on Nvidia and with AMD on Ubuntu. I think what you are suggesting is I try the ROCm driver on my Fedora system. I did try that early on with no success, but perhaps I should try again now that I have more experience with video drivers.

There must be something different. When using the ROCm driver I can run Einstein@home, but Milkway@home will instantly stop with a computation error. I think the ROCm driver should be preferred since AMD is moving everything to opensource instead using the opencl bits from closed pro driver.

There must be something different. When using the ROCm driver I can run Einstein@home, but Milkway@home will instantly stop with a computation error. I think the ROCm driver should be preferred since AMD is moving everything to opensource instead using the opencl bits from closed pro driver.

I agree. From what I've read ROCm is the way to go. When I get a chance I will look into that again.

Thanks to the successful testing by Speedy51, I will be able to deploy the Windows Nvidia OpenCL app. I should get to that in the next couple hours.

In the meantime, has anyone with an AMD card on linux tried to test that version? I deployed it ~12 hours ago and no tasks have been sent out yet. My own system cant seem to download tasks for it either, so I think something might be wrong with how I setup the plan class.

I just deployed the windows Nvidia version as a beta app. Please test and report any suspicious behavior.

Feel free to send me the openCL Windows app via mail. Would like to give it a try. :)

I just sent you the AMD version, since I now have confidence in Nvidia version. Thanks!

Runtime from a sf5 task: 1 hour and 3 minutes; which is ~3 times faster than a CPU task.
Runtime from a sf6 DS7x10: ~7 minutes, which i cant relate to a CPU task at this time.

No errors while running the task.
It seems to work fine, at least for me. :)

The Nvidia windows version seems to be doing pretty well. Many successful results from multiple users. Only 2 compute errors.

I am going on a road trip (vacation) for a week. I will have cell phone coverage, but unable to do any major project maintenance. I will look into the above compute errors when I return.

Have a nice vacation. I will try to complete as much GPU tasks as i can. ;)

Thanks to the successful testing by Speedy51, I will be able to deploy the Windows Nvidia OpenCL app. I should get to that in the next couple hours.

In the meantime, has anyone with an AMD card on linux tried to test that version? I deployed it ~12 hours ago and no tasks have been sent out yet. My own system cant seem to download tasks for it either, so I think something might be wrong with how I setup the plan class.

I have AMD cards but use Windows so I can't help sorry.

---

The Nvidia windows version seems to be doing pretty well. Many successful results from multiple users. Only 2 compute errors.

I am going on a road trip (vacation) for a week. I will have cell phone coverage, but unable to do any major project maintenance. I will look into the above compute errors when I return.

I found the bug that was causing the compute errors. It's minor and affects less than 1% of the WUs. I will get a fix out there later this evening.

The estimated runtime for results with the new version is very, very wrong.

They show a runtime of 22 seconds on my host but take about an hour to finish.

The estimated runtime for results with the new version is very, very wrong.

They show a runtime of 22 seconds on my host but take about an hour to finish.

That's because CreditNew restarts the stats calculations with each new app version. I'm not sure exactly how to change it's initial value. I too saw this last night, but by this morning it is now estimating 25 minutes per task, which is accurate for my GPU.

The estimated runtime for results with the new version is very, very wrong.

They show a runtime of 22 seconds on my host but take about an hour to finish.

That's because CreditNew restarts the stats calculations with each new app version. I'm not sure exactly how to change it's initial value. I too saw this last night, but by this morning it is now estimating 25 minutes per task, which is accurate for my GPU.

So I believe CreditNew uses rsc_fpops_est as it's initial starting point. This was at least 10x too low. I have now fixed this, so going forward the initial flops estimates should be better.

The beta apps are functioning as intended, yes?

Will we see a Windows app for opencl_amd?

---

The beta apps are functioning as intended, yes?

Will we see a Windows app for opencl_amd?

Yes, thanks for reminding me. The nvidia apps have been working well, so I just promoted them to normal app status. There is still some room for optimization, but the apps are stable, so I think this is a good idea.

There are a couple people helping with the amd opencl versions. Exact same opencl code that works perfectly on nvidia, but amd cards are very finicky. I believe it comes down to inconsistent drivers. The amd opencl on linux had about half a dozen successful results which is a good sign.

I removed the beta designation on the AMD opencl linux version. Although there were relatively few results, those that tested the beta version did so successfully. I will keep an eye on results; if problems arise I will revert back to beta status.