| log in |
Message boards : Application Code Discussion : CUDA for Milkyway@Home
| Author | Message |
|---|---|
|
Because it looks like the server can handle a bit more work, I've uploaded the CUDA code for plain milkyway@home, and it's in the code release directory. Hopefully we'll be able to just use CUDA code for regular milkyway@home and then we wouldn't even need to start up milkywayGPU@home. | |
| ID: 25013 | Rating: 0 | rate:
| |
|
How will that work with the single precision cards? Won't the searches eventually reach a point where they won't be accurate enough anymore? | |
| ID: 25026 | Rating: 0 | rate:
| |
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning. ^^ From the front page.. Does this mean when you put it back up, that we Cuda users can download the app and try crunching on that? The download link you posted http://milkyway.cs.rpi.edu/milkyway/download/code_release/ Is a little confusing ..to say the least. | |
| ID: 25029 | Rating: 0 | rate:
| |
Hopefully we'll be able to just use CUDA code for regular milkyway@home and then we wouldn't even need to start up milkywayGPU@home. I'm very confused by this... I thought you were wanting to issue much larger tasks to GPUs so that you could do things that CPUs wouldn't be able to handle quickly enough? What happened with that? Also, unless you're seeing a relatively large stockpile of tasks waiting to be sent, and I don't think < 1000 qualifies as "large", then I think that there is a high probability that people will figure out that things are working better here now, bring more processing power over, and then we'll be back in the same situation... Make sure that you're planning for a longer time horizon than just a few weeks.... | |
| ID: 25030 | Rating: 0 | rate:
| |
Because it looks like the server can handle a bit more work, I've uploaded the CUDA code for plain milkyway@home, and it's in the code release directory. Hopefully we'll be able to just use CUDA code for regular milkyway@home and then we wouldn't even need to start up milkywayGPU@home. I would be ready. I can release a single precision ATI version today if you want. But be warned, SP is about a factor 4 or more faster than DP per WU! The server should be prepared for that combined rush (a lot of CUDA GPUs + lower end ATI cards adding to the higher end ATIs already in use). Have you thought about the credit issue? Just giving the single precision clients half that of the DP ones isn't going to cut it. The single precision variant actually does quite a bit less operations than the double precision one because all used functions have hardware implementations. For instance one doesn't have to do the quite expensive exp() in software (like in DP or also on CPUs [done in the math library]). All in all the number of really executed operations for the SP version (have to thoroughly count it, will tell you the result) is almost exactly halved. I think it would be best to use exactly the same credit multiplier as SETI which also GPUGrid converges to (2.72 credits per SP TeraFlop, here at MW the current value for DP is 7.5, one may think about lowering it to 5.44, i.e. twice the SP value). Together with the lower count of the operations for SP it will most likely result in about the same credit/time rate as when using DP on the same GPU (at least on ATI, for nvidias GTX2xx cards SP would yield most likely a higher credit rate than DP). But how do you differentiate between the SP and DP versions? By using the applications version string? Or should one introduce an additional SP marker to the out file? | |
| ID: 25033 | Rating: 0 | rate:
| |
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning. Yeah, I'll have a binary for OS X that you can try and crunch with. ____________ | |
| ID: 25034 | Rating: 0 | rate:
| |
Talking to my advisors it seems they don't want us to release a single precision application for GPUs for milkyway@home just yet. I think that will have to wait until we get milkyway GPU up and running. The single precision binaries I'm going to release are just for testing really (i'd like to see how many machines my code works on).
Yeah we're going to have to come up with a credit scheme for milkywaygpu that takes into account floating point and double precision apps (double precision getting more credit because their results are more accurate and useful.
____________ | |
| ID: 25035 | Rating: 0 | rate:
| |
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning. So no support for Windows yet? All my machines run Windows.. :( | |
| ID: 25036 | Rating: 0 | rate:
| |
Talking to my advisors it seems they don't want us to release a single precision application for GPUs just yet. So no chance for any GPU older than the GTX2xx line of nvidia or the mainstream series of ATI (besides the HD4700 series which supports DP)? | |
| ID: 25037 | Rating: 0 | rate:
| |
Talking to my advisors it seems they don't want us to release a single precision application for GPUs just yet. I edited my post :) We're going to have floating point on milkywayGPU whenever I get the backend up and running, but not here for the time being. ____________ | |
| ID: 25038 | Rating: 0 | rate:
| |
Talking to my advisors it seems they don't want us to release a single precision application for GPUs just yet. I edited my post :) We're going to have floating point on milkywayGPU whenever I get the backend up and running, but not here for the time being. ____________ | |
| ID: 25039 | Rating: 0 | rate:
| |
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning. I don't have a windows box to compile and test it on, so no. Another student who should be taking over most of the GPU work, Anthony, does I think. So we should have those when he gets up to speed (or when one of our users releases one). ____________ | |
| ID: 25042 | Rating: 0 | rate:
| |
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning. Travis I think you misunderstood ztmike here. The CUDA code release can only be tested on the test WUs ztmike, not for the main project itself (yet). Also Travis, if you are going to deploy the CUDA DP at normal MW, will this not require a BOINC upgrade server side? This would be so people can select 'Use CUDA app' in their preferences, akin to SETI, rather just randomly issue CUDA Wus to CUDA machines, like in Aqua@Home. It would be interesting if MW_GPU changed its name to MW_SP :) Such that the older cards (and some of the new cards) could go over there. ____________ | |
| ID: 25045 | Rating: 0 | rate:
| |
|
Hi there, | |
| ID: 25160 | Rating: 0 | rate:
| |
|
CUDA is for NVidia graphics cards. You have an ATI graphics card. There might already be a GPU application for you (unless it doesn't support double precision). | |
| ID: 25162 | Rating: 0 | rate:
| |
|
Yes Please Cluster, can you make it if possible so it works on X series ATI cards? It would be greatly appreciated... | |
| ID: 25163 | Rating: 0 | rate:
| |
Yes Please Cluster, can you make it if possible so it works on X series ATI cards? It would be greatly appreciated... All ATI HD series will work with the MW GPU project (most likely even the integrated chipsets like 780G), where single precision will be enough. In the moment it is simply not possible, because they don't support the required precision. But for the X series there may be no simple solution as they are not supported by the Stream SDK. One would have to write some DirectX shaders (or use the old BrookGPU) to get it to work and I don't know if they support the required features. | |
| ID: 25168 | Rating: 0 | rate:
| |
|
Apple is only going to support OpenCL on a very limited amount of GPU's. Graphics and OpenCL ____________ | |
| ID: 25190 | Rating: 0 | rate:
| |
|
Is anybody even compiling/testing M@H Cuda app for Windows? Not sure why Windows was not supported first, as most people have that OS.. | |
| ID: 25213 | Rating: 0 | rate:
| |
|
Well i've finally managed to get CUDA working properly on the Mac Pro. Not bad considering it's a slow old 8800GT. | |
| ID: 25243 | Rating: 0 | rate:
| |
|
Thanks for the info not such an easy task it would appear...... | |
| ID: 25245 | Rating: 0 | rate:
| |
|
Glenn, it may well be very easy. It's been almost 10 years since I did anything related to Unix commands. So getting CUDA itself to work is probably far easier than I found it. I found an idiots guide. | |
| ID: 25251 | Rating: 0 | rate:
| |
Well i've finally managed to get CUDA working properly on the Mac Pro. Not bad considering it's a slow old 8800GT. Do you have any performance figures to share? trisf told us a 9600GT on a C2D 6750 took about 15 minutes for the wedge 20 test unit. These test WUs are quite small so the execution time may be somehow limited by the CPU and all the calling overhead for the GPU stuff. Nevertheless it would be interesting to have a comparison with the 8800GT. | |
| ID: 25264 | Rating: 0 | rate:
| |
|
I tried to run ps_sgr_214F_2s* on my 9600gt and self compiled linux64 binary... | |
| ID: 25275 | Rating: 0 | rate:
| |
|
Gday Satan, I dont have any code writing experience or i would have a go at it myself and my ATI X1300 only handles single precision so it looks like i have to upgrade my graphics card...May have go trolling for some info on what my card is actually capable of... | |
| ID: 25284 | Rating: 0 | rate:
| |
I tried to run ps_sgr_214F_2s* on my 9600gt and self compiled linux64 binary... Yes, the production WUs are quite bit larger than the test WUs. As the code for MW_GPU does quite a bit more with one WU as the legacy MW@home code (roughly 300 or 400 times as much for the WU you tried to run, would have to check it to give an exact number), it is normal for them to take several hours. The fastest GPUs out there complete these WUs in about 50 seconds with the "classic" algorithm, albeit in double precision. Multiplying that time with 400 equals 5.5 hours. Such long WU were one of the goals of MW_GPU actually. That slow and sluggish behaviour of the GUI is a side affect of GPU apps with a very high utilization of the GPU. The ATI app also suffered (and still does to some extent) from this. One has to limit the duration of the GPU kernels somehow. That creates short opportunities for other tasks (like the screen refresh) to execute which will result in a smoother experience. The high CPU load should be easy to cure. One only have to send the application to sleep (a millisecond is enough) when it busy waits for the completion of a GPU kernel. That should be one line in the code (at least I hope so). | |
| ID: 25294 | Rating: 0 | rate:
| |
|
Cluster, | |
| ID: 25325 | Rating: 0 | rate:
| |
Will have a go over the next couple of days. I keep screwing something up because it keeps telling me that not target has been set. Will need to go through take a slow careful look at what i'm screwing up. That could be the problem. Don't know how it works on a Mac, but under Win and Linux you have to attach a monitor to the card. Otherwise it is not active and one can't run anything on the GPU. | |
| ID: 25329 | Rating: 0 | rate:
| |
|
I had no trouble getting it to run under BootCamp without a display connected. I don't know whether it is something in the Apple drivers or not, but I can run the CUDA examlples such as oceanFFT no problems and they show perfectly fine. | |
| ID: 25374 | Rating: 0 | rate:
| |
|
According to Nvidia the requirement of having to attach a monitor is a strange Microsoft requirement that they could work around - but not without breaking WHQL certification. I don't know the deal with Linux though. | |
| ID: 25375 | Rating: 0 | rate:
| |
I had no trouble getting it to run under BootCamp without a display connected. I don't know whether it is something in the Apple drivers or not, but I can run the CUDA examlples such as oceanFFT no problems and they show perfectly fine. Not really, I don't know hardly anything about software/driver developing. I am pretty good on app_info's up to when they added all that fplops to the mix. ____________ | |
| ID: 25376 | Rating: 0 | rate:
| |
|
Or even... | |
| ID: 25380 | Rating: 0 | rate:
| |
|
There is a way around the monitor bug thing in windows without using a second monitor or a dummy plug. | |
| ID: 25407 | Rating: 0 | rate:
| |
Will have a go over the next couple of days. I keep screwing something up because it keeps telling me that not target has been set. Will need to go through take a slow careful look at what i'm screwing up. On the new macbook pros, you need to go into system preferences -> energy saver then select higher performance to use the other (faster) GPU. If you don't want to use that there's a line in evaluation_gpuX.cu which sets the device (it's at 1, i think it should be changed to 0 to use the on-chip GPU). ____________ | |
| ID: 25537 | Rating: 0 | rate:
| |
|
Trying to obtain results for linux_x86_64 cuda gpu http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=81905297
and some stderr.txt
wu is still runnning | |
| ID: 25827 | Rating: 0 | rate:
| |
|
I'll give it ago when Travis posts the updated code files. I can't say that i will have any success though. | |
| ID: 25832 | Rating: 0 | rate:
| |
Trying to obtain results for linux_x86_64 cuda gpu http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=81905297 As this is a 2 stream WU with a double sized wedge, I can give some comparison with a a HD3870 (overclocked to 860MHz). I've not run a whole WU yet (takes too long ;)), but I know the time for a single evaluation. As the the number of evaluations is given in the output file, I can say that HD3870 would take about 8000 seconds (2:15 hours) for the 447 evaluations (roughly 18 seconds per evaluation). This number is deduced from a normal sized wedge, so there is some uncertainty to it (maybe 20%). What graphics card do you use? Was it a 9600GT? It has 64 stream processors, opposed to the 112 to 128 of the 8800GT/GTX, 9800GT/GTX series. That would mean a G92 based graphics card is roughly as fast as a HD3870 with the current code, depending on the clock and the exact number of enabled units also a bit faster. The GT200 would battle it out with the HD4800 series then ;) | |
| ID: 25894 | Rating: 0 | rate:
| |
|
Thanks CP. | |
| ID: 25921 | Rating: 0 | rate:
| |
|
In the BOINC manager options menu check the enable manager exit menu check box then ok. Then file exit..the dialog box should have the checkbox stop science applications when exiting manager make sure this is checked click ok. That should be it | |
| ID: 25942 | Rating: 0 | rate:
| |
Trying to obtain results for linux_x86_64 cuda gpu http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=81905297 By the way, there may be a bug in the CUDA version when initializing the stream_c parameters. If one compares the init_constants function from the CPU version if (ap->sgr_coordinates == 0) {
atGCToEq(ap->stream_parameters[i][0], 0, &ra, &dec, get_node(), wedge_incl(ap->wedge));
atEqToGal(ra, dec, &l, &b);
} else if (ap->sgr_coordinates == 1) {
gcToSgr(ap->stream_parameters[i][0], 0, ap->wedge, &lamda, &beta); //vickej2
sgrToGal(lamda, beta, &l, &b); //vickej2
} else {
printf("Error: sgr_coordinates not valid");
}
lbr[0] = l;
lbr[1] = b;
lbr[2] = ap->stream_parameters[i][1];
lbr2xyz(lbr, stream_c[i]); with the beginning of gpu__likelihood gc_to_gal(wedge, stream_parameters(i,0) * D_DEG2RAD, 0 * D_DEG2RAD, &(lbr[0]), &(lbr[1]));
lbr[2] = stream_parameters(i,1);
d_lbr2xyz(lbr, stream_c); one sees the CUDA version lacks the if statement for the SGR coordinates. Actually the CUDA version assumes that no SGR coordinates are used. At least this is how I read the code, the rotation matrix used in gc_to_gal is the same as in atEqToGal. I will stay with the CPU code version of that for the time being ;) | |
| ID: 25954 | Rating: 0 | rate:
| |
|
@Travis: | |
| ID: 26141 | Rating: 0 | rate:
| |
|
Are there any news about the CUDA App for MW (running on Windows) ? | |
| ID: 26754 | Rating: 0 | rate:
| |
|
Hi all, i have a video card based on nvidia 8600GT | |
| ID: 27864 | Rating: 0 | rate:
| |
|
is there ANY NEW NEWS on a CUDA app for MW????? | |
| ID: 28386 | Rating: 0 | rate:
| |
|
Anthony Waters Posted this 18 Jul 2009 1:55:17 UTC Hello, Anthony Waters Posted this 24 Jul 2009 21:58:58 UTC The GPU app will go up as a beta application on the regular Milkyway@Home site when it is ready. ____________ | |
| ID: 28407 | Rating: 0 | rate:
| |
|
Travis Posted 22 Jul 2009 5:02:47 UTC We actually have a working CUDA double precision app running right now, our new researcher Anthony is working on it. I think he's going to be releasing it as a beta application in the next week or so -- the only issue is that we're having an issue with the likelihood calculation that we want to resolve, when that happens we'll have to update all the applications. | |
| ID: 28427 | Rating: 0 | rate:
| |
|
Here is a new release of the GPU App source (v0.08) | |
| ID: 28652 | Rating: 0 | rate:
| |
(Binaries for Windows and Linux included) from the readme: it takes around 90 seconds to execute on a GTX 285 By the way, the test WUs supplied in that package have the size of the (now quite rare) ~18 credits (stripes 79, 82, 86) or ~27 credit (stripes 20, 21) WUs. | |
| ID: 28654 | Rating: 0 | rate:
| |
|
Cluster Physik, | |
| ID: 28655 | Rating: 0 | rate:
| |
Cluster Physik, In the moment it is compatible. The project has still to figure out what they want to change ;) And I really don't know what is up with the new Catalyst drivers. In some configurations under Vista it runs quite well, but WinXP is a no go with anything newer than 9.2. If I find the reason, I will of course update the apps. | |
| ID: 28656 | Rating: 0 | rate:
| |
|
Hi development, i try to run milkyway cuda gpu on my 8600GT, but is not supported (cuda 1.1) you have drop the support under 1.3? | |
| ID: 28665 | Rating: 0 | rate:
| |
|
CUDA 1.3 is required for Double Precision support, single precision was tried, however, it only gave accuracy to 6/7 decimal places which is not enough. | |
| ID: 28667 | Rating: 0 | rate:
| |
|
So it will not work on my 8800 GTS as well? | |
| ID: 28672 | Rating: 0 | rate:
| |
CUDA 1.3 is required for Double Precision support, single precision was tried, however, it only gave accuracy to 6/7 decimal places which is not enough. then your volunteers just took a nose-dive... i only have one card 1.3 compatible which is a gtx 260.... my 2 other cards are 9400 gt which are 1.1..... | |
| ID: 28673 | Rating: 0 | rate:
| |
CUDA 1.3 is required for Double Precision support, single precision was tried, however, it only gave accuracy to 6/7 decimal places which is not enough. It is the same restriction as for ATI GPUs. | |
| ID: 28675 | Rating: 0 | rate:
| |
|
Yep, excludes a lot more people though due to Nvidia's reluctance to move to double precision. Are there still plans to make a single precision GPU sister project? | |
| ID: 28677 | Rating: 0 | rate:
| |
|
So this will only work on GTX cards? I have 9800GT cards -- sounds like I'm not in the lucky subset at the moment. CUDA 1.3 is required for Double Precision support, single precision was tried, however, it only gave accuracy to 6/7 decimal places which is not enough. ____________ | |
| ID: 28680 | Rating: 0 | rate:
| |
|
gpugrid has currently | |
| ID: 28682 | Rating: 0 | rate:
| |
|
Sorry zpm. You must be at least this tall to ride the attraction. | |
| ID: 28683 | Rating: 0 | rate:
| |
|
what, do i have to be as tall as Shaq. i'm 6'11" as is.... | |
| ID: 28684 | Rating: 0 | rate:
| |
|
Hehe, I sympathize with you. I have quite a few of those older cards available as well. I guess the project really needs the precision and those "older" GPU's aren't quite up to the task. | |
| ID: 28685 | Rating: 0 | rate:
| |
|
Does this mean no single precision app for ati either? | |
| ID: 28699 | Rating: 0 | rate:
| |
Does this mean no single precision app for ati either? Thats correct. Milkyway@Home really requires double precision accuracy for what we're doing. There are too many numerical issues if we go to single precision. ____________ | |
| ID: 28700 | Rating: 0 | rate:
| |
|
-------------------------------------------------------------------------------- | |
| ID: 28701 | Rating: 0 | rate:
| |
Here is a new release of the GPU App source (v0.08) Saw this in the ReadMe .. -Windows users need to use the 32 bit version 32bit version of what? BOINC? Because I downloaded the 64bit version.. | |
| ID: 28729 | Rating: 0 | rate:
| |
|
CUDA 2.2 Toolkit and appropriate driver listed on NVIDIA's website[1] | |
| ID: 28730 | Rating: 0 | rate:
| |
Wait..so I need Nvidas 32bit GPU drivers to be able to run this? Why would someone delete their 64bit GPU drivers to download 32bit drivers to run this on their spare time? Unless, I'm missing something here? | |
| ID: 28733 | Rating: 0 | rate:
| |
meaning the 32 bit version CUDA 2.2 Toolkit, sorry for the confusion Wait..so I need Nvidas 32bit GPU drivers to be able to run this? Why would someone delete their 64bit GPU drivers to download 32bit drivers to run this on their spare time? Unless, I'm missing something here? If that's how it is..it sounds like this is in Alpha stage. | |
| ID: 28734 | Rating: 0 | rate:
| |
|
32 bit version of the CUDA 2.2 Toolkit, you can use 32bit or 64bit drivers, sorry for the confusion | |
| ID: 28744 | Rating: 0 | rate:
| |
|
I clicked on the bat file..then clicked on the .exe file, and I got this: | |
| ID: 28760 | Rating: 0 | rate:
| |
|
Looks like you haven't installed the CUDA 2.2 Toolkit? Windows should automatically reference in the files like cudart.dll. | |
| ID: 28774 | Rating: 0 | rate:
| |
Looks like you haven't installed the CUDA 2.2 Toolkit? Windows should automatically reference in the files like cudart.dll. Okay..now I downloaded the Cuda Toolkit and rebooted, now I get an error of: "The application was unable to start correctly (0xc000007b). Click OK to close the application." I am doing it right, right? Click on the Windows BAT file then click on the .exe? When I click on the BAT file 2 window things go onto my desktop, with the names of "Out" and "Stderr" ..I believe it shows them on my picture in my last post, are those files suppose to be on the desktop? I realize this is testing ..but these directions suck. I hope you guys aren't going to make it this hard for when it launches. | |
| ID: 28792 | Rating: 0 | rate:
| |
|
It'll only launch when the application has been fully integrated into BOINC. | |
| ID: 28801 | Rating: 0 | rate:
| |
It'll only launch when the application has been fully integrated into BOINC. This will be the final release version that goes on BOINC pending any bugs and the new likelihood fixes. Also this release is more of a "does this work on other people's machines besides mine" so don't expect it to run with BOINC Emanuel, you seem to be contradicting Anthony? I realize this is testing ..but these directions suck. I hope you guys aren't going to make it this hard for when it launches. Yes this is testing - to see if it works on other CUDA developers machines. Of course it'll be more straight forward than this - BOINC has the CUDA infrastructure to cope for it just to be added. Then it's a case of making sure you have the right driver. As for the windows zip file, just loaded it on my work machine where I do most of my CUDA coding. Opened the .sln in VS08 and it's complaining it can't find the file Cuda.Rules: Custom build rules file 'mw_gpu_v0.08\milkyway\bin\Cuda.Rules' was not found or failed to load. App doesn't work here on a case of it's not a CUDA machine - was hoping to load it in VS then run in emu mode. I'll try on my CUDA machine at home in due course. ____________ | |
| ID: 28809 | Rating: 0 | rate:
| |
1. Check the file stderr.txt for the detailed error message 2. Verify that in the same folder of the executable there is a file named astronomy_parameters.txt, stars.txt, and search_parameters.txt. If there is not then the set_parameters.bat file was run incorrectly, it needs to be executed from the command line and given a command line argument. Please see http://commandwindows.com/ if you are unfamiliar with the command line. Alternatively if you cannot get the command line to work you can copy and rename the file astronomy_parameters-20.txt to astronomy_parameters.txt, stars-20.txt to stars.txt and search_parameters-20.txt to search_parameters, this is effectively what the batch file does, except instead of using 20 it uses the number that was passed in as the command line argument. 3. From the looks of it your using Vista/Win7 so it might be an Operating System specific issue, I have personally only tested it on Windows XP x64 and Linux/GNU 64 bit When it launches through BOINC the application will download and automatically run without user intervention, unless an error occurs with initializing the GPU. As for the directions, any ideas as to what to include to make them better? I tried to write them as detailed as possible but it is always hard to imagine how so many different people can interpret a piece of writing, especially if they are unfamiliar with the subject. | |
| ID: 28846 | Rating: 0 | rate:
| |
I have a lacking of expertise with respect to Visual Studio, especially the latest versions, so I'm not quite sure how to setup the solution and project files in a machine independent way. If you look in the same directory as the project file you will notice that the Cuda.Rules file is located in there, if you could update Visual Studio to use that file it should update the path and correctly load the file. I think the place where you specify the Build Rules is under the project settings menu (Right click on the project) and navigate to Custom Build Rules I realized that after I wrote the above paragraph that I neglected to include the actual file in the release, since the paragraph still sort of applies I chose not to delete it. Here is the Cuda.Rules file http://milkyway.cs.rpi.edu/milkyway/download/code_release/ | |
| ID: 28847 | Rating: 0 | rate:
| |
1. Check the file stderr.txt for the detailed error message Nothing in there but this: "" As far as doing number 2 of what you said..you completely lost me on that one, I think I'll just sit this one out. I never done this sort of thing, but I just wanted to help to get this Cuda project on its knees faster. Hopefully you guys have people testing this besides whats been said in this thread so far..because honestly its looking a little sparse for testers. I run Windows 7 64bit with a dual boot of Ubuntu 9.04 ..which I'm still learning, if I'm having this much trouble on Windows, I don't think I'm going to be trying it on Linux. | |
| ID: 28858 | Rating: 0 | rate:
| |
I realized that after I wrote the above paragraph that I neglected to include the actual file in the release, since the paragraph still sort of applies I chose not to delete it. Here is the Cuda.Rules file http://milkyway.cs.rpi.edu/milkyway/download/code_release/ Thanks Anthony :) ____________ | |
| ID: 28863 | Rating: 0 | rate:
| |
|
Damn, project does not accept new users :( | |
| ID: 28927 | Rating: 0 | rate:
| |
Damn, project does not accept new users :( There is no project for the CUDA application, unless you are referring to something else? Right now the CUDA application is currently in alpha stage for community preview and will be joining the regular Milkyway@Home project as a Beta application once the likelihood issue is resolved. | |
| ID: 28936 | Rating: 0 | rate:
| |
|
Ah, so how do I join it? | |
| ID: 28938 | Rating: 0 | rate:
| |
|
What that means is that CUDA will be on the regular MW project and the GPU one will most likely go away as they got the server straitened out. | |
| ID: 28939 | Rating: 0 | rate:
| |
...will go away as they got the server straitened out. Until a gazillion new hosts attach here running CUDA. ;) ____________ Calm Chaos Forum...Join Calm Chaos Now | |
| ID: 28947 | Rating: 0 | rate:
| |
[quote]...will go away as they got the server straitened out. If they ever do. Each 'fix' tends to break things. Until a gazillion new hosts attach here running CUDA. ;) Listen carefully for the 'BOOM'. ;) ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 28948 | Rating: 0 | rate:
| |
|
What ever happened to the plan to substantially increase the science done for GPU tasks, providing much longer running work units? Will this still happen here at this project? | |
| ID: 28959 | Rating: 0 | rate:
| |
...will go away as they got the server straitened out. not going too happen b/c of single precision not being accepted...1.3 compatible only... and i don't see all the users at gpugrid which have 1.3 comp cards coming over here.. no offense to milkyway.. only reason they would come is if... A. work from the project they like, is fresh out of work.. and the secondary project that they use when this happens runs out of work.. B. Project they like goes down for some reason... C. problems with certain individual computers. | |
| ID: 28962 | Rating: 0 | rate:
| |
|
So how exactly i put my GF cards to work this on Vista X64? | |
| ID: 28966 | Rating: 0 | rate:
| |
So how exactly i put my GF cards to work this on Vista X64? Right now, you can't. Once the CUDA application is finished, you can attach to whatever project hosts it (we still don't know if it'll be Milkyway or Milkyway_gpu), and BOINC 6.4.x or later should pick up the GPU app automatically. ____________ | |
| ID: 28984 | Rating: 0 | rate:
| |
It'll only launch when the application has been fully integrated into BOINC. You're right, I think I misinterpreted what he said. You can understand "don't expect it to run with BOINC" as "BOINC wouldn't be able to run the program" or "BOINC can run the program but we're not sending out GPU-specific work-units yet" and I interpreted it as the former, but I guess it's the latter. That is, pending any bugs and the new likelihood fixes :) By the way, how would such GPU-specific WUs (that do more work) be sent out to the CAL app? Could it pretend to be a CUDA app, or would it be have to be a special case server-side? | |
| ID: 28994 | Rating: 0 | rate:
| |
|
As I understand it BOINC does not support the notion of GPU-specific WUs. When the version of the milkyway application is updated the client asks the server what application to download. If there exists a CUDA 1.3 capable card the client will download the CUDA application, otherwise, the CPU version will be downloaded. Then this application is used for every WU that gets processed. | |
| ID: 29049 | Rating: 0 | rate:
| |
|
Confused, what Gpu card to by next, ati or nvidia, nvidia has more project accepting, but ati seems faster here, someone get me a answer, please? | |
| ID: 29176 | Rating: 0 | rate:
| |
|
When MW will relased CUDA app, all will be clear, We will be able to do direct comparision ATI vs Nvidia.... | |
| ID: 29203 | Rating: 0 | rate:
| |
When MW will relased CUDA app, all will be clear, We will be able to do direct comparision ATI vs Nvidia.... I attached MW_gpu 3 mouths ago. I have ever recieved any CUDA WU. And now My account of MW_gpu has been deleted by server. It denied my login and refuse to accept I reattach it....... I think CUDA is an impossible mission for MW_gpu...... | |
| ID: 29204 | Rating: 0 | rate:
| |
When MW will relased CUDA app, all will be clear, We will be able to do direct comparision ATI vs Nvidia.... For one, the CUDA application isn't even finished yet, so there's no way you could've downloaded CUDA work from it. As for the account problems, that was probably caused by the database crash not long ago that affected the main project too. ____________ | |
| ID: 29211 | Rating: 0 | rate:
| |
When MW will relased CUDA app, all will be clear, We will be able to do direct comparision ATI vs Nvidia.... The Milkyway_GPU project has been closed because the CUDA application will be on the regular Milkyway@Home project. The only step left is updating the server side BOINC software, once that is done the CUDA application will be released on BOINC as a beta application. I am unable to give a time estimate for when the server side BOINC software will be upgraded because the upgrade cannot be done by me, it has to be done by the staff that controls the server that Milkyway@Home is hosted on. An alpha community preview of the CUDA application can be found in this post http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=906&nowrap=true#28652 | |
| ID: 29231 | Rating: 0 | rate:
| |
As I understand it BOINC does not support the notion of GPU-specific WUs. When the version of the milkyway application is updated the client asks the server what application to download. If there exists a CUDA 1.3 capable card the client will download the CUDA application, otherwise, the CPU version will be downloaded. Then this application is used for every WU that gets processed. Does that mean that any project utilizing CUDA won't run anymore CPU units alongside it? (as I understand it the GPU client does hundreds of times more work, but still) | |
| ID: 29307 | Rating: 0 | rate:
| |
As I understand it BOINC does not support the notion of GPU-specific WUs. When the version of the milkyway application is updated the client asks the server what application to download. If there exists a CUDA 1.3 capable card the client will download the CUDA application, otherwise, the CPU version will be downloaded. Then this application is used for every WU that gets processed. I'm not 100% sure but I think the way it works is as follows: (Hardware - Resulting Applications) 1 CPU - 1 CPU Application Runs 2 CPUs - 2 CPU Applications Run 1 CPU and 1 GPU - 1 GPU Application Runs 2 CPUs and 1 GPU - 1 GPU Application Runs and 1 CPU Application Runs | |
| ID: 29319 | Rating: 0 | rate:
| |
2 CPUs and 1 GPU - 1 GPU Application Runs and 1 CPU Application Runs It depends on how strong the GPU-app uses a CPU, too. Regarding GPUGrid and Collatz Conjecture, the CPU-utilization is almost 0%, so that you really have 2 CPU apps and 1 GPU app running! The CUDA-Code over at AQUA however was bad, took too much CPU-time, and other apps were affected by that. ____________ Member of BOINC@Heidelberg and ATA! My BOINCstats | |
| ID: 29495 | Rating: 0 | rate:
| |
|
For those of you worrying about the double precision requirement, there are other projects which do not require double precision accuracy and you can put your less well endowed cards on. (I don't have a CC 1.3 card.) | |
| ID: 29502 | Rating: 0 | rate:
| |
The only step left is updating the server side BOINC software, once that is done the CUDA application will be released on BOINC as a beta application. Why hasn't this been done yet? How long is this Cuda app planned to be in Alpha stage? | |
| ID: 29506 | Rating: 0 | rate:
| |
|
With the server upgrade now in place work has begun on setting up the server to be able to distribute the CUDA client to users that have access to a CUDA 1.3 card (one that supports double precision). Right now a Linux/GNU 64 Bit CUDA application is live, however, there are some issues with the NVIDIA drivers and BOINC so the application seg faults. This issue should be non-existant on Windows, therefore, over the next few days a Windows 32 bit CUDA client will be added to the server. | |
| ID: 29619 | Rating: 0 | rate:
| |
|
Nice! | |
| ID: 29620 | Rating: 0 | rate:
| |
With the server upgrade now in place work has begun on setting up the server to be able to distribute the CUDA client to users that have access to a CUDA 1.3 card (one that supports double precision). Right now a Linux/GNU 64 Bit CUDA application is live, however, there are some issues with the NVIDIA drivers and BOINC so the application seg faults. This issue should be non-existant on Windows, therefore, over the next few days a Windows 32 bit CUDA client will be added to the server. i'll be happy to do a test run for yall considering the new drivers suck for a lot of users and can't use them.. 190.62 is working fine for me on gpugrid, seti, and Einstein. ____________ I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/ | |
| ID: 29637 | Rating: 0 | rate:
| |
Nice! I'm having difficulties building 64bit Windows applications with Visual C++ Express Edition so there will only be a 32 bit application in the beginning. | |
| ID: 29662 | Rating: 0 | rate:
| |
Nice! what exactly is the trouble? libraries? | |
| ID: 29664 | Rating: 0 | rate:
| |
The CUDA compiler from NVIDIA is giving me some trouble with using the 64 bit binaries of the Visual C++ compiler (cl.exe). It complains of the wrong version, I'm researching the problem now. | |
| ID: 29691 | Rating: 0 | rate:
| |
Visual C++ Express Edition doesn't include the 64 bit SDK. You need to download and install that to be able to compile and link a 64 bit app. Anyway, there's no use for an 64 bit CUDA app since you won't gain any speed by using 64 bits and any 64 bit windows can run 32 bit app. Problem solved, case closed :p ____________ Join BOINC United now! | |
| ID: 29695 | Rating: 0 | rate:
| |
|
So any news on status update for Cuda for Windows? ETA? | |
| ID: 29696 | Rating: 0 | rate:
| |
|
The Windows 32 bit application is complete and I have successfully downloaded it through BOINC and crunched about 5 WUs. I have deprecated it though because it is getting different results than older versions of the code, as a result of a few changes in the code repository. Right now I am waiting on a response from the team to see if it is okay if the code changes propagate to the users. As for an ETA, it will be any day now, pending on the conclusion of the code change. | |
| ID: 29698 | Rating: 0 | rate:
| |
|
i was looking at the apps page, what is this: | |
| ID: 29699 | Rating: 0 | rate:
| |
|
What will be the supported gpu 260+ ? and what is the supported boinc version 6.47+ ? | |
| ID: 29719 | Rating: 0 | rate:
| |
|
The latest source code for CUDA is now up at http://milkyway.cs.rpi.edu/milkyway/download/code_release/mw_gpu_v.zip | |
| ID: 30525 | Rating: 0 | rate:
| |
|
I need help | |
| ID: 34299 | Rating: 0 | rate:
| |
|
There appears to be a memory fault with the longer wu's with the app using over 300MB of video RAM, instead of ~30MB. If you only run 1 wu at a time it seams to help. | |
| ID: 34300 | Rating: 0 | rate:
| |
There appears to be a memory fault with the longer wu's with the app using over 300MB of video RAM, instead of ~30MB. If you only run 1 wu at a time it seams to help. thanks So I set up incorrectly nothing that pleases me ;-) nice greetings | |
| ID: 34303 | Rating: 0 | rate:
| |
|
This issue should be resolved in the latest version (0.24) available on BOINC. | |
| ID: 34343 | Rating: 0 | rate:
| |
This issue should be resolved in the latest version (0.24) available on BOINC. which is not available in code repository... | |
| ID: 34398 | Rating: 0 | rate:
| |
This issue should be resolved in the latest version (0.24) available on BOINC. Thanks for the reminder http://milkyway.cs.rpi.edu/milkyway/download/code_release/mw_gpu_v0.24.tar http://milkyway.cs.rpi.edu/milkyway/download/code_release/mw_gpu_v0.24.zip | |
| ID: 34419 | Rating: 0 | rate:
| |
Message boards :
Application Code Discussion :
CUDA for Milkyway@Home