First CUDA App for Windows available for Beta Test
3 Aug 2009 15:50:42 UTC
Topic 13767
(moderation:
The first Einstein@home CUDA App for Windows is available for Beta Test at Beta Test Page.
This is a big package to download (17MB), as it contains both applications (S5R5 and ABP1).
We are still new to writing app_info.xml files for CUDA applications. The one contained in this package should allow to run one ABP1 task per CUDA device, occupying a full CPU core for support, and run S5R5 tasks on the remaining CPU cores.
There are no entries for older than the latest App versions 3.05 / 3.07 in the app_info.xml, tasks already assigned to older Apps will error out.
The ABP1 CUDA App has undergone limited testing with a BOINC CC 6.6.36 and a 181.20 NVidia Driver on a GTX285 system. We can confirm that the App doesn't crash immediately on such a setup, but not much more. We already ran into some mysteries of the CC scheduler, though.
Again, this is our very first experience with CUDA Applications, please bear with us and don't expect everything to work right away.
Please test and report, and please include important information (like the NVIdia Driver and Core Client version) in your posts.
BM
BM
First CUDA App for Windows available for Beta Test
)
Currently the application only uses CUDA for the FFT, the other calculations are still done on the CPU. I think the CPU part is still the bottleneck. This will change in the future.
BM
BM
The lib/dll thing was my
)
The lib/dll thing was my mistake, the package did work on our machines because CUDA was installed there.
I replaced the .libs by the (hopefully) correct .dlls in the package and in the app_info.xml (and updated the md5 sum on the Beta page).
BM
BM
RE: Bernd, Would you rather
)
If it works with the CUDA 2.3 libs, that's fine with me. I guess this depends also on BOINC and your driver version; we found it not working on our machines with 2.2 libs and the corresponding driver (189 IIRC).
Outdated. I saw this too and removed it when updating the page for the Linux Beta App.
BM
BM
If you run into problems
)
If you run into problems before any tasks have been reported, PLEASE specify your system (BOINC Core Client Version, NVidia Hardware, Driver version, Windows version, whatever applies).
Otherwise any help could be only wild guessing.
BM
BM
RE: Still no validator
)
Running, but still digging through the results that piled up over the weekend (see server status page - the workunits "waiting for validation" are all ABP1).
BM
BM
RE: if only we could see
)
Yep, that's on my wishlist for some time now.
The problem is that ABP1 workunit generator and validator are running on a remote machine in Hannover, Germany, not on the main project server.
When I find the time I may let the machine in Hannover serve a html frame that can be embedded in the UWM SSP.
BM
BM
Regarding CPU usage see my
)
Regarding CPU usage see my previous message. We let some calculations run on the CUDA device (GPU), but I think the current App is still CPU bound, i.e. it does more work on the CPU than on the GPU. We're working on changing this, but this will take some more work & time. We released this App nevertheless to use this time to already gain some experiece with CUDA in the BOINC environment.
BM
BM
Does anybody happen to know
)
Does anybody happen to know or has the patience to try out how to write an app_info.xml that can run a CUDA version of an application on each CUDA device and a CPU version of the same application (here: einsteinbinary_ABP1) on the remaining CPU cores?
BM
BM
RE: Is it just me, or does
)
My fault. Fixed.
BM
BM
We posted a new CUDA App for
)
We posted a new CUDA App for Windows that fixes a bug and should be a little faster on the CPU, too. See here.
BM
BM