CUDA App einsteinbinary 3.10 for Windows available for Beta Test |
Message boards : Cruncher's Corner : CUDA App einsteinbinary 3.10 for Windows available for Beta Test
| Author | Message |
|---|---|
|
A new Einstein@home CUDA App for Windows is available for Beta Test at Beta Test Page. | |
| ID: 98830 | | |
|
Hello all readers, | |
| ID: 98834 | | |
How can I get S5 WU's to crunch? It could be your BOINC version. You could try a 6.6.x version, but probably they have other flaws. (I'm out of that - no CUDA, still 5.x :-) Gruß, Gundolf | |
| ID: 98835 | | |
How can I get S5 WU's to crunch? Thanks for the idea Gundolf, but at other projects I had read that versions from 6.5.x and beyond are not stable. To be shure I always follow a few months later, and do never install the latest version. I cracked the solution myself in the meantime to set the aditional work buffer at a higher rating. ____________ Greetings from TJ | |
| ID: 98838 | | |
|
First task back - 136845395 - in just a shade over 6 hours - very similar to previous run, on the same host as I used last time. So no discernable benefit from the SSE code. | |
| ID: 98844 | | |
|
Hi, | |
| ID: 98845 | | |
Is it possible to cruch on 2(gpu+cpu) and 2 cpu? To use the remaining two cores, you'll have to enable a non-GPU application, either from Einstein (includes merging app_info.xml files - for advanced users only) or from another project. Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 98847 | | |
|
Installed this on my host running Windows 7 64-bit, it started ok! | |
| ID: 98849 | | |
Is it possible to cruch on 2(gpu+cpu) and 2 cpu? I wanna do that. What do I have to do? (edit which lines?) hotze ____________ | |
| ID: 98850 | | |
|
20/08/2009 11:58:41 Einstein@Home Message from server: To get more Einstein@Home work, finish current work, stop BOINC, remove app_info.xml file, and restart. | |
| ID: 98851 | | |
Hi, Hi Hotze33, The nVidia 9800GT-card has only one processor so it can only handle one GPU-WU at a time. A GTX295 has two processors and can handle thus 2 GPU_WU’s at the same time. There are also some quatro cards and off course the Tesla-cards (specially designed for parallel computing). But al these are expensive. If you set the “Additional work buffer” to i.e. 0.50 (as I did) then after a while you get a S5R5 to crunch or a WU from another project you are participating (if any). Hope this helps. ____________ Greetings from TJ | |
| ID: 98852 | | |
20/08/2009 11:58:41 Einstein@Home Message from server: To get more Einstein@Home work, finish current work, stop BOINC, remove app_info.xml file, and restart. GPU units run on GPU and CPU. AFAIK GPU calculates FFT and GPU everything else. To run GPU task, you have to modify app_info.xml, as stated in last posts. BTW: app_info.xml of last beta version allowed CPU work, did that change? Michael ____________ Team Linux Users Everywhere ![]() | |
| ID: 98853 | | |
BTW: app_info.xml of last beta version allowed CPU work, did that change? Oops, my bad. Sorry, Hotze, you should be able to receive CPU and GPU tasks with the beta app_info.xml, without modifications. Gruß, Gundolf | |
| ID: 98854 | | |
|
My 2 wu with 3.10 were almost exactly the same run time as with previous version. | |
| ID: 98855 | | |
|
I can now process GPU work! With the previous 3.09 version, I errored out immediately. | |
| ID: 98858 | | |
I can now process GPU work! With the previous 3.09 version, I errored out immediately. thats what i was going to ask if any one has tested or finished a wu with a gtx 260 b/c gpugrid has had troubles with this card... i have one with 190.38 and will test this version to see if it runs... just got to dl all this stuff. @RB, what manufacturer is the card? EDIT!: GTX 260 running app now, WUIP: http://einstein.phys.uwm.edu/result.php?resultid=136872957 | |
| ID: 98868 | | |
..i have one with 190.38 and will test this version to see if it runs... just got to dl all this stuff. Congratulations! Btw, my card is manufactured by EVGA. And it worked on GPU Grid. ____________ Regards, Bob P. | |
| ID: 98870 | | |
|
First unit completed under win 7 64-bit on a GeForce 9600GT. | |
| ID: 98876 | | |
|
Finished. Win 7 x64, 190.38, 6.6.37. | |
| ID: 98885 | | |
Finished. Win 7 x64, 190.38, 6.6.37. Using CUDA device #0 "GeForce GTX 260" (806.98 GFLOPS) WT* is that. no offense, but I'm very hesitate to believe those numbers... what are the specs of that card????? MHZ? the damn card better be; Liquid cooled, running at 800 mhz.... please post the message logs of the boinc start-up... ok, nvm; i'll admit i'm quick to jump to conclusions.... holmis's reports 300 gflops as well, is the app mis-reading the gflop number????????????????????? | |
| ID: 98887 | | |
|
Ok, | |
| ID: 98889 | | |
Using CUDA device #0 "GeForce GTX 260" (806.98 GFLOPS) Reported five tasks on host 1001564 - two validated so far, three pending. Times all very close to 6 hours, no significant change from 3.07cuda. Card is a 9800GT, stock speed, rated at 60 BOINC GFlops, but reported here as 508.03 NVidia marketing GFlops (as also shown in the GPUGrid FAQ). I've commented before that there's a factor of 8 or 9 between 'marketing' and 'crunching' GFlops - it doesn't matter which you use for card comparison purposes, so long as you always state which units you're using, and don't mix them. | |
| ID: 98892 | | |
Ok, Hi Hotze, Off course that card has 2 processors, I was thinking at SLI and then they work as one. If you like cuda you could take a look at GPUGRID, for about 7 hours work you can get 4000-5000 credits. ____________ Greetings from TJ | |
| ID: 98893 | | |
Yes. However, some part of the app will still run on the CPU - it'll never be "pure". We aim to reduce the amount of work done on the CPU as much as we can of course.
No, it's not. You need to know that this value is computed by the device properties and not determined by benchmarks. It's the card's theoretical maximum performance which can be computed like this: number of multiprocessors * number of cores/multiprocessor * clock rate * flop/core/cycle. For your GTX 260 that's 24 * 8 * 1.4 GHz * 3. By the way, is this an overclocked card? Usually they "only" run at 1.3 GHz... No one claimed that either your card or any given application could realistically achieve that performance ;-) As always, you may relatively compare different cards using the same measure, despite the absolute values not being very informative. Cheers, Oliver | |
| ID: 98895 | | |
And we imagine that the GPU will continue to improve in the speed of processing as well, which of course will yield even more efficiency! :) ____________ Regards, Bob P. | |
| ID: 98897 | | |
thanks, sometimes i go nutz... | |
| ID: 98900 | | |
Card is a 9800GT, stock speed, rated at 60 BOINC GFlops, but reported here as 508.03 NVidia marketing GFlops (as also shown in the GPUGrid FAQ). I've commented before that there's a factor of 8 or 9 between 'marketing' and 'crunching' GFlops - it doesn't matter which you use for card comparison purposes, so long as you always state which units you're using, and don't mix them. Ah, so that's why. So 1 BGFlop ~= 8 NVMGFlops [aside] Reminiscent of : - the 1 MB vs 1 million bytes issue ( and GB .... ) - the Cyrix processor's 'Performance Rated' speed ( 'as good as a Pentium' vs actual ) - the quoting of CD drive speeds ( angular or linear velocity? ) [/aside] Cheers, Mike. ____________ "I have made this letter longer than usual, because I lack the time to make it short." - Blaise Pascal | |
| ID: 98903 | | |
|
new driver available, 190.62, which is working fine on my vista machine. | |
| ID: 98911 | | |
|
a new wu run under 190.62. works fine. | |
| ID: 98922 | | |
Card is a 9800GT, stock speed, rated at 60 BOINC GFlops, but reported here as 508.03 NVidia marketing GFlops (as also shown in the GPUGrid FAQ). I've commented before that there's a factor of 8 or 9 between 'marketing' and 'crunching' GFlops - it doesn't matter which you use for card comparison purposes, so long as you always state which units you're using, and don't mix them. BOINC is telling us a much lower figure. This is funny because when you put a ATI card in with it their cards are reported as being much faster (by BOINC) under 6.10.0. While there is differenced between the cards the formula needs to be standardised, at least in the BOINC world. ____________ BOINC blog ![]() | |
| ID: 98924 | | |
|
my last cuda wu finished in 5-6 hrs rt. | |
| ID: 98925 | | |
my last cuda wu finished in 5-6 hrs rt. Hi, is your Q6600 overclocked or running at default speed? I´m looking for some performance numbers between different cards. I want to know, which card gives the most bang for the buck. hotze ____________ | |
| ID: 98926 | | |
my last cuda wu finished in 5-6 hrs rt. 2.4 260 216 core is my card and i'm running the newest driver... 295 is 2*240 core so it's the most bang for buck; but, be sure your power supply can handle it... i think the gtx 295 can knock it out, with i7 is under 2 hrs if benchmarks are any key.. | |
| ID: 98929 | | |
Reminiscent of : 1 MB equals 1 million bytes - officially, anyway. There are binary prefixes for use with Bytes, i.e. MiB. Unfortunately, no operating system currently in existence honors these prefixes. (and Mebibyte doesn't sound quite as charming as Megabyte) | |
| ID: 98933 | | |
295 is 2*240 core so it's the most bang for buck; but, be sure your power supply can handle it..... Don't agree with you there, ZPM. The GTX295 is certainly the most powerful card, so the most bang... ...but for the buck? I don't think so. Compared with single-processor 240 shader cards such as the GTX275, the shader clock is slower, so you don't get twice the performance: but you pay more than twice the price. I reckon you get almost 25% more bang for the buck with a 275, compared with the 295. | |
| ID: 98935 | | |
|
I have crunching a CUDA WU with a GTX 285 in 5,5 hours. My wingmen has crunched the same WU with a CPU in 6 hours. | |
| ID: 98936 | | |
|
@ Einstein@home: I have crunching a CUDA WU with a GTX 285 in 5,5 hours. My wingmen has crunched the same WU with a CPU in 6 hours. Post the system specs, It's all BETA. So the more details the better. Speed should be ecpected (grow in future) better or am i wrong. | |
| ID: 98937 | | |
@ Einstein@home: OK : ASUS P5E3 Q9300 2x1 Gb DDR3 1333 GTX 285 190.38 Vista Ultimate BOINC 6.6.36 The other task was crunched with a X7900 - Darwin 9.8.0 ____________ | |
| ID: 98945 | | |
|
If I understand correctly then the current run is a cuda assisted cpu run. The gpu is used for some calculations but not all. Right now your are mainly limited by the cpu. The gpu gives you just a boost of ca. 20-50%. | |
| ID: 98947 | | |
If I understand correctly then the current run is a cuda assisted cpu run. The gpu is used for some calculations but not all. Right now your are mainly limited by the cpu. The gpu gives you just a boost of ca. 20-50%. Ok, we'll see then :-) Thanks ____________ | |
| ID: 98948 | | |
|
I have been getting the same sort of errors within seconds of starting execution, both on 3.07 and 3.10: <core_client_version>6.6.36</core_client_version> <![CDATA[ <message> The system cannot find the path specified. (0x3) - exit code 3 (0x3) </message> <stderr_txt> Activated exception handling... [10:30:57][9612][INFO ] Starting data processing... [10:30:57][9612][INFO ] Using CUDA device #0 "GeForce 8500 GT" (44.06 GFLOPS) [10:30:57][9612][INFO ] Checkpoint file unavailable: status.cpt (No such file or directory). ------> Starting from scratch... [10:30:57][9612][INFO ] Header contents: ------> Original WAPP file: p2030_54162_47225_0054_G48.85-01.81.C_4.wapp ------> Sample time in microseconds: 128 ------> Observation time in seconds: 268.9792 ------> Time stamp (MJD): 54162.546585648146 ------> Number of samples/record: 512 ------> Center freq in MHz: 1440 ------> Channel band in MHz: 0.390625 ------> Number of channels/record: 256 ------> Nifs: 1 ------> RA (J2000): 192747.923054 ------> DEC (J2000): 131107.828389 ------> Galactic l: 48.7926 ------> Galactic b: -1.8848 ------> Name: G48.85-01.81.C ------> Lagformat: 0 ------> Sum: 1 ------> Level: 3 ------> AZ at start: 348.1477 ------> ZA at start: 5.1279 ------> AST at start: 0 ------> LST at start: 0 ------> Project ID: p2030 ------> Observers: Kevin ------> File size (bytes): 16190754 ------> Data size (bytes): 16179201 ------> Number of samples: 2097152 ------> Trial dispersion measure: 186.6 cm^-3 pc ------> Scale factor: 7711.9 [10:30:58][9612][INFO ] Seed for random number generator is 1009522123. [10:31:00][9612][ERROR] Error creating CUDA FFT plan (error code: 2) [10:31:00][9612][ERROR] Demodulation failed (error: 3)! called boinc_finish </stderr_txt> ]]> Host number is 480469 The WUs appear to fail with both the CUDA 2.1 and 2.3 DLLs - the driver version installed is 190.38. Am I missing something really obvious? The host runs SETI CUDA WUs okay. I am not complaining, just reporting - I know improvements can't be made without reports from testers. ____________ Soli Deo Gloria | |
| ID: 98949 | | |
|
Since we had a new binary for CUDA processing, I thought I'd run a few WUs to see if the situation had improved. Also running 3.05 WUs on the second cpu for the system. | |
| ID: 98952 | | |
If I understand correctly then the current run is a cuda assisted cpu run. The gpu is used for some calculations but not all. Right now your are mainly limited by the cpu. The gpu gives you just a boost of ca. 20-50%. The CPU is needed to feed the GPU from time to time and the GPU sends it back. So the CPU can be seen as a "handler" in the process. So for now there will be always a bit of help from the CPU (until they find other ways to handle). ____________ Greetings from TJ | |
| ID: 98954 | | |
I have crunching a CUDA WU with a GTX 285 in 5,5 hours. My wingmen has crunched the same WU with a CPU in 6 hours. Hello, I run the einstein cuda-app on a i7 with a GTX285. It takes about 4.7-5 hours to complete, while I have seen wingman with faster CPU's (non-cuda) and they take 7-8.3 hours to complete. So I see a difference. ____________ Greetings from TJ | |
| ID: 98955 | | |
I have crunching a CUDA WU with a GTX 285 in 5,5 hours. My wingmen has crunched the same WU with a CPU in 6 hours. I crunched a 3.10 using my CPU only, and found that compared to using the GPU it was about 80% as fast. In other words, the GPU crunches 20% faster than CPU by itself. As others have commented, the GPU has a lot of potential I believe to become much faster while using less of the CPU. :) ____________ Regards, Bob P. | |
| ID: 98956 | | |
Since we had a new binary for CUDA processing, I thought I'd run a few WUs to see if the situation had improved. Also running 3.05 WUs on the second cpu for the system. I've changed my mind on the following...comparing apples/oranges.
The above is false because I'm trying to compare E@H WUs to APB1 WUs. I tried searching around for some non-CUDA APB1 WUs, but they've all rolled out of my stats. The rest of this post is valid though.
| |
| ID: 98960 | | |
I crunched a 3.10 using my CPU only, and found that compared to using the GPU it was about 80% as fast. In other words, the GPU crunches 20% faster than CPU by itself. For a while there it seemed that the collective BOINC CUDA channeling was working. It seemed that the GPU was only using a small fraction of the CPU. But that seems to have dissipated for the time being with E@h. It seems we have a ways to go before we get to significant throughput increases of the magnitude we had hoped. Like others here though, I suspect it might take a while but we will eventually see some very significant improvements in throughput. It's slow going, but we'll get there. :-) ____________ ![]() (Click for detailed stats) | |
| ID: 98963 | | |
|
Hi, | |
| ID: 98983 | | |
|
To the developers, | |
| ID: 98985 | | |
|
This app has started fine on my 9800 GT. Thanks for developing an app compatible with 64-bit Vista/Win7! Other specs: Q9550, BOINC 6.6.36, Driver 190.38, v2.3 dll's. 2009-08-24 17:28:20.6143 [PID=24659] [HOST#1758399] Sending [RESULT#137355097 h1_0892.30_S5R4__928_S5R5a_1] (est. dur. 14987.39 seconds) It sent S5R5 work despite not finding an app for it? Or maybe it wanted an S5R5 CUDA entry. My app_info includes 3.05 for S5R5, 3.09 for CPU ABP1 and 3.10 for CUDA ABP1. Edit - link to scheduler log, spelling ____________ ![]() | |
| ID: 98987 | | |
|
I've found how to run 4 S5R5 tasks while working on ABP1 on CUDA device. | |
| ID: 99005 | | |
|
Hi Wedge009, I have been getting the same sort of errors within seconds of starting execution, both on 3.07 and 3.10: Sorry, not enough memory. Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps... Cheers, Oliver | |
| ID: 99006 | | |
I've found how to run 4 S5R5 tasks while working on ABP1 on CUDA device. Thanks Stranger, It's simple and it's works fine. That I didn't find this myself... ____________ Greetings from TJ | |
| ID: 99007 | | |
Sorry, not enough memory. Thank you for taking the time to answer, this explanation is really helpful. I just wish BOINC wouldn't try to keep asking for GPU work on Einstein, though. The server keeps telling me to remove the app_info.xml, but I'm using the 3.09 ABP beta application since it appears to be show a speed improvement over the current 3.08 release, and it's taking a long time for BOINC to ask for CPU work instead (since there's a four-hour delay after each GPU work request). ____________ Soli Deo Gloria | |
| ID: 99023 | | |
I just wish BOINC wouldn't try to keep asking for GPU work on Einstein, though. The server keeps telling me to remove the app_info.xml, but I'm using the 3.09 ABP beta application since it appears to be show a speed improvement over the current 3.08 release, and it's taking a long time for BOINC to ask for CPU work instead (since there's a four-hour delay after each GPU work request). It is simple. You should increase your WU buffer by changing time interval for which you want BOINC to keep up running and after next connection to server you should start slowly decreasing this buffer to an apropriate value. It is in BOINC settings - Client configuration - Network settings. | |
| ID: 99033 | | |
|
Ugh, really? I don't like keeping huge buffers. Unlike some other people, I don't like hogging WUs by having a 10 day cache. ): | |
| ID: 99042 | | |
Ugh, really? I don't like keeping huge buffers. Unlike some other people, I don't like hogging WUs by having a 10 day cache. ): givin the recent streek of downtime i dont think anyone would mind it. i personally used to keep a 1 day cache. untill the intermitant downtimes. now i keep a 7 day cache "just in case" and no, i dont blame anyone at the project for the downtime. stuff happens. ____________ seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift. | |
| ID: 99048 | | |
|
I rarely visit some machines and have to set cache to 10 days and more in case of server failure. Of cause I don't use unstable machines for this. | |
| ID: 99051 | | |
Hi Wedge009, Hi Oliver I wonder if you someone would be kind enough to state what the system requirements are which are planned to go into the scheduler. I just wasted a few hours getting setup to "Play" with the Beta on my 8400GS to get the same error on 2 WU's Regards ____________ | |
| ID: 99057 | | |
Hi Wedge009, I don't suppose my 128Mb 8400M GS will work eithier then?, is there a CPU fallback mode? :D Claggy | |
| ID: 99138 | | |
|
My first WU just completed in 9 hours with no problems. | |
| ID: 99141 | | |
|
Well, I put 10 days for connection and 10 days for work cache... and still Einstein is only asking work for the GPU and waiting 4 hours thereafter. This is... a little frustrating. | |
| ID: 99172 | | |
...For the record, this is BOINC 6.6.36, the latest stable release. Well, it is the recommended version; that doesn't mean it's stable or bug free ;-) Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 99173 | | |
|
I've given up. To get Einstein CPU WUs, I have to leave the GPU information in the app_info.xml and just put up with the repeated errors on the GPU WUs. As long as there are no GPU WUs across all projects, the scheduler will always ask for GPU WUs first. ): | |
| ID: 99199 | | |
I've given up. To get Einstein CPU WUs, I have to leave the GPU information in the app_info.xml and just put up with the repeated errors on the GPU WUs. As long as there are no GPU WUs across all projects, the scheduler will always ask for GPU WUs first. ): If your CUDA card doesn't have enough memory to run this app, wouldn't it be better to devote your testing efforts to the parallel CPU-only v3.09 test, and relieve the servers of all that wasted download pressure? | |
| ID: 99202 | | |
|
You misunderstand. That's what I've been trying to do. 3.09 works great and seems to be a substantial improvement over 3.08, so that's why I've been trying to run it instead of just removing the app_info.xml altogether as the Einstein server keeps yelling at me to do. But no matter what I try, BOINC insists on giving priority to requesting GPU WUs before CPU ones. I strongly recommend releasing 3.09, it seems to be thoroughly tested now. | |
| ID: 99213 | | |
You misunderstand. That's what I've been trying to do .... Maybe I'm missing something but if you really are trying to get CPU tasks rather than GPU tasks, why don't you ditch the GPU app_info.xml and set up the CPU one instead? You said earlier that you "have to leave the GPU information in the app_info.xml". I'm sorry but this is quite wrong - you certainly don't have to do that. You should re-read Richard's advice because he doesn't misunderstand and he's suggesting exactly what you need to do. Here are some important points for you to consider:-
| |
| ID: 99274 | | |
|
First of all, I meant no offence. I know this is all volunteer-run. Maybe I'm missing something but if you really are trying to get CPU tasks rather than GPU tasks, why don't you ditch the GPU app_info.xml and set up the CPU one instead? Because I had already set up a CPU-only app_info.xml previously. It appears that BOINC detects the presence of a GPU on this particular host and will request GPU units regardless of the fact that there is no GPU application included in the app_info.xml. And it is because of the fact that there are no GPU applications in the app_info.xml that the Einstein server responds with the "remove app_info.xml" message and will then set a four-hour delay for the next communication with it. You said earlier that you "have to leave the GPU information in the app_info.xml". I'm sorry but this is quite wrong - you certainly don't have to do that. I agree! I shouldn't! But the fact is that - on this particular host, at least - until there is some GPU work on the system already, BOINC refuses to request CPU work from the Einstein server. Lots of people on many projects are complaining about scheduling problems in 6.6.36. Well... I wasn't aware of this, but after my recent experience, I can see why. If you don't want GPU capability, something like 6.4.7 or 6.5.0 should be much better for you. The problem is that I do. SETI GPU units work fine on this host. The unfortunate thing is that recent WU shortages from SETI means that there is no GPU work available. Hence BOINC asking Einstein for some, regardless of the fact that there is no corresponding GPU application in the app_info.xml. Setting 10/10 for your cache sizes is likely to worsen the already bad behaviour of 6.6.36. If you are 'always on' use something like 0/1 to 0/4. Again, I agree. I was simply following Stranger7777's suggestion from earlier. My default cache is 0.5/0 and I already expressed my reluctance to use such an unreasonably large cache size previously. The EAH project has some sort of server bug that causes the scheduler to say randomly that it has no tasks available even if it has just given you some. With S5R5 this causes a 1 min backoff before a retry is done. With ABP1, the backoff is 4 hours. You don't have to endure the 4 hour backoff. Just wait 1 min and then force a retry with the 'update' button. Once you have sufficient tasks on board, the backoff shouldn't bother you any further. I am aware that one can force a server request with the update button. Unfortunately, this is not helpful when BOINC keeps requesting GPU units. <sigh> In any case, hopefully my woes will all become moot shortly. I'm waiting on a replacement video card to come in which will surely be sufficient for processing the Einstein GPU WUs. ____________ Soli Deo Gloria | |
| ID: 99275 | | |
[quote]* If you don't want GPU capability, something like 6.4.7 or 6.5.0 should be much better for you. Hi Gary, Yust for information. I run GPU WU's (CUDA) with 6.4.7 and it works fine. Jobs take about 4 hours with a "cold" graphics card and all are validated, some still pending. I never use the latest version of BOINC. ____________ Greetings from TJ | |
| ID: 99279 | | |
|
And how is the the 3.10 doing. | |
| ID: 99332 | | |
First of all, I meant no offence. I know this is all volunteer-run. No offense was taken - sorry if my reply implied offense. Maybe I'm missing something ... Ahhh, OK. I had read your previous messages and had interpreted the statements about BOINC requesting GPU work in preference to CPU work as meaning that you were setup for both. I didn't notice any statement about having a CPU only app_info.xml so I thought you hadn't made the change back to CPU only - which was why I asked the question/made the comment. If using the AP mechanism, my previous experience (on older BOINCs) says that BOINC wont ask for work for an app that is not in app_info.xml. If more recent BOINCs do ask, this is unfortunate as it removes a degree of control from the user. It would be interesting to know if you reverted to 6.4.7 or 6.5.0, would you be able to get E@H CPU work through AP (without BOINC asking for GPU work) whilst still getting Seti CUDA work for your low memory GPU? <sigh> In any case, hopefully my woes will all become moot shortly. I'm waiting on a replacement video card to come in which will surely be sufficient for processing the Einstein GPU WUs. Even with your new video card, you may still have issues with 6.6.36. You may find you can better control your mix of projects/apps by using 6.4.7 or 6.5.0. I've seen many people reporting good behaviour with those versions. ____________ Cheers, Gary. | |
| ID: 99348 | | |
It appears that BOINC detects the presence of a GPU on this particular host and will request GPU units regardless of the fact that there is no GPU application included in the app_info.xml. And it is because of the fact that there are no GPU applications in the app_info.xml that the Einstein server responds with the "remove app_info.xml" message and will then set a four-hour delay for the next communication with it. Ok, here's what's happening. BOINC 6.6.36 has separate CPU and GPU work fetch schedulers. When a GPU is detected, the GPU work fetch scheduler will start running and try to fetch work from whichever project you are attached to. This can be considered as a ping to the project, to check if they have a GPU application available. When a project has no GPU application available, you'll see this work request pass by a couple of times, with ever increasing gaps between tries, until it will only ask once a day as it'll be on a 24 hour back-off. That's what your four hour delay does as well, if you just let it continue, the next time it's an 8 hour delay, 16 hour, 24 hour. What you do with the anonymous platform app_info.xml file is specifically tell BOINC only to use the applications specified in the file, none of the others. It won't disable the specific work request schedulers, those will continue until the maximum back-off time is reached. It's not pretty, but it works quite well. So you can go back to an app_info.xml file with only CPU applications and then just ignore the messages about the file from the GPU work request. They'll minimize and only pass by once a day after that, with any luck in the middle of your night. ____________ Jord -The BOINC FAQ Service -CUDA/CAL Stream FAQ | |
| ID: 99349 | | |
|
I seemed to get a 4-hour wait every time, not the increasing intervals each time as you described. | |
| ID: 99357 | | |
|
Tested with Nvidia driver version 190.62 on GeForce GTX 280. | |
| ID: 99387 | | |
|
Hi, | |
| ID: 99547 | | |
Hi, Seems to be a bad link to some files "Das System kann den angegebenen Pfad nicht finden" is boinc installed in a different place Maybe the *.xml needs to be edited. PS: Any updated speed improvement (20% is too small to be usefull). | |
| ID: 99566 | | |
|
I am a q9400, win7, 4GB ram, GTX275 | |
| ID: 99684 | | |
|
the following wu got an error immediately (tried also updating cudart and cudafft dlls to 2.3 but didn't work) | |
| ID: 99692 | | |
|
I just want to share my experience with the cuda app. As I mentioned earlier about half of the workunits get an calculation error: | |
| ID: 99699 | | |
...For me it seems more like a scheduler problem. The result is running out of memory on the gpu and than have no empty ram and so killing a wu. Yes, and if I recall correctly, it was fixed in 6.6.38 and a 6.10.x version after 6.10.4. Gruß, Gundolf | |
| ID: 99701 | | |
...For me it seems more like a scheduler problem. The result is running out of memory on the gpu and than have no empty ram and so killing a wu. Ok I will give it a try. But 6.6.38 has another bug (atleast in win7 64bit). It only recognizes 1 graphicscard. The second card is not detected. 6.5 is working fine so far. I will try 6.6.38 in winxp later. hotze ____________ | |
| ID: 99703 | | |
...For me it seems more like a scheduler problem. The result is running out of memory on the gpu and than have no empty ram and so killing a wu. Not detected, or detected but not used? If you have two graphics cards of different specifications, BOINC v6.6.xx (and v6.10.xx) is designed only to use the "most capable". You can change that by setting the <use_all_gpus>1</use_all_gpus> configuration flag documented in client configuration. | |
| ID: 99705 | | |
Not detected, or detected but not used? Not detected. I have 2 9800GX2 from the same vendor with the same specifications. 6.6.38 in winxp 32 seems good so far. Running on all 4 gpus and not killing wus. One gpu is running in a PCIe16x slot and the other is in a PCIe4x slot. There is no significant difference in runtime yet. So there is some room for performance improvement ;) hotze ____________ | |
| ID: 99706 | | |
|
BOINC 6.6.38 (winxp32 sp3) hasn´t trashed any wu so far. But I have seen a runtime variance between the gpus in the PCIe16 slot and the PCIe4 slot (which is reasonable). | |
| ID: 99723 | | |
|
Just so you folks know, for 6.10.x the only "usable" versions are .3, .7, and .11 based on experiences on GPU Grid, Collatz, MW ... oh, and my own personal use. :) | |
| ID: 99759 | | |
|
I am mostly running 6.10.11 and 6.10.7 -- I think I have a few other iterations out there -- probably need to address that -- though I tend not to change until properly burned on a specific workstation... Just so you folks know, for 6.10.x the only "usable" versions are .3, .7, and .11 based on experiences on GPU Grid, Collatz, MW ... oh, and my own personal use. :) ____________ ![]() | |
| ID: 99767 | | |
|
Quite all my CUDA Wu are aborting with a "Compute error" after 4-5 elapsed hours. | |
| ID: 99773 | | |
|
No reason to change if there is no problem or you don't need a feature. I had been moving up because of the need for ATI support and then left it on a couple machines even after I moved cards about. | |
| ID: 99774 | | |
Quite all my CUDA Wu are aborting with a "Compute error" after 4-5 elapsed hours... Your tasks abort with the "Maximum elapsed time exceeded" message. Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 99777 | | |
|
Quite all my CUDA Wu are aborting with a "Compute error" after 4-5 elapsed hours... | |
| ID: 99781 | | |
|
"Maximum elapsed time exceeded" | |
| ID: 99783 | | |
|
"Maximum elapsed time exceeded" | |
| ID: 99784 | | |
|
how much % improvement to CPU only. | |
| ID: 99788 | | |
|
Hi! | |
| ID: 99797 | | |
|
@Bikeman | |
| ID: 99830 | | |
@Bikeman Thanks for testing! The way BOINC works here it will be a bit difficult to set reasonable resource limits for WUs that can be processed by either COU or GPU tasks, but at least the early aborts can be fixed now. CU Bikeman ____________ ![]() ![]() | |
| ID: 99837 | | |
|
what is the hidden point of use expensive graphic cards and get boring 20% of perfomance increase? | |
| ID: 99841 | | |
what is the hidden point of use expensive graphic cards and get boring 20% of perfomance increase? It's not "hidden", it's public... Oliver | |
| ID: 99847 | | |
i mean why so small advantage of using gpu? | |
| ID: 99848 | | |
Well, I tried to explain it: this is a first test using a trivial approach. We will tune the application for maximum performance as we go... Oliver | |
| ID: 99849 | | |
ok. i will wait for "fermi" and change my current nvidia to ati ) | |
| ID: 99850 | | |
...In the meantime until the devs have responded: if you are courageous, you can try the following (experts only, and only if you get this nasty -177 error!!!: Wouldn't it be better to introduce the <flops> directive into the app_info.xml file? I don't know much about it, since I don't have a CUDA device, but from reading on the SETI boards, it sounds as if it could help. Here's a short reminder of the "Maximum elapsed time exceeded" error: The splitters provide both <rsc_fpops_est> used to estimate runtime, and 10 times that as <rsc_fpops_bound> used to determine when work has run so long that BOINC should kill it with a "Maximum elapsed time exceeded". BOINC uses DCF in the estimate but not in the max. If DCF were 1, a VLAR which wasn't rebranded would be killed at 10 times the estimate, if DCF were 0.1 it would have to run 100 times the estimate to reach the max limit. Obviously, the <flops> directive can be used to "adjust" the DCF to be consistent between different applications (and to be lower than 1, which helps avoid the error). Here's another thread from the SETI boards, where the p_fpops to flops conversion is shown. The values of course have to be evaluated anew here at Einstein. Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 99856 | | |
|
Hi Gundolf, | |
| ID: 99860 | | |
|
started my first einstein beta unit on my homeserver with 9600 GT card | |
| ID: 99863 | | |
started my first einstein beta unit on my homeserver with 9600 GT card http://einstein.phys.uwm.edu/forum_thread.php?id=7539&nowrap=true#99848 ____________ seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift. | |
| ID: 99864 | | |
...So, as the cuda beta app's runtime is in the same order of magnitude as the CPU variant, would it make sense to set <flops>x</flops> then to (say) half the value of <p_fpops> in your client_state.xml ? I hope you aren't asking me :-) since I have no experience with that matter. I'd say try 0.5 (or perhaps 0.25 of estimated GFlops?) and watch DCF behaviour, thus using trial and error - unless someone else shows up with a sound analytical approach. Gruß, Gundolf | |
| ID: 99866 | | |
|
David Anderson checked in changeset [19282] less than an hour ago, apparently in response to this problem. | |
| ID: 99867 | | |
|
Indeed, that change is related to the discussion here and is basically reverting an earlier change. If you are using a BOINC version older than 6.10.5 you probably are not affected by this problem anayway (problem = result terminated prematurely by BOINC because BOINC thinks it is in an endless loop as it's resource limit was exceeded). | |
| ID: 99868 | | |
|
Task ID 142450599 | |
| ID: 99872 | | |
Task ID 142450599 Hi! This error seems to be caused by what we were discussing a few messages ago in this thread: Newer BOINC versions will perform the calculation of the maximum runtime per result differently. To fix this, you can try the following: - shutdown Boinc - Find the app_info.xml file, it should be in it should be "C:\Documents and Settings\All Users\Application Data\BOINC\projects\einstein.phys.uwm.edu" or similar. -insert this line after the line ending in </plan_class>: <flops>3000000000.0</flops> - save modified app_info.xml - restart BOINC Hope this helps, Bikeman ____________ ![]() ![]() | |
| ID: 99875 | | |
Hi! Darn i had forgotten to save the file when i edit it ____________ ![]() | |
| ID: 99882 | | |
|
I want to crunch einstein only on the gpu and don´t want to download any cpu work. Is this possible? | |
| ID: 100098 | | |
|
I stopped this beta since every unit gets aborted or reported as in error | |
| ID: 100115 | | |
I want to crunch einstein only on the gpu and don´t want to download any cpu work. Is this possible? You can opt-out of the ABP1 workunits (the only ones having a GPU app currently) via the web-interface, but there is no way to opt-out of the Gravitational Wave Search in LIGO data (S5R5) for which only CPU apps are available. It's a decision of the project administration, so this is intended. CU Bikeman ____________ ![]() ![]() | |
| ID: 100142 | | |
I want to crunch einstein only on the gpu and don´t want to download any cpu work. Is this possible? You'd have to adjust your app_info.xml file to only contain references to the CUDA application(s). Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 100143 | | |
|
Maybe a bit over the top for the developers. | |
| ID: 100206 | | |
how long shall we wait for this application? | |
| ID: 100234 | | |
The engineer in me is tempted to say "'till it's ready" :-). Seriously tho, remember that the ABP1 Binary Pulsar Search is relatively young: While E@H started several years ago, the ABP1 search began only in March this year. CUDA support in BOINC also is rather new, and for my personal taste, Boinc 6.10.x is the first release that really handles GPU tasks reliably wrt. task scheduling, resource shares etc. CU Bikeman ____________ ![]() ![]() | |
| ID: 100302 | | |
|
Some more speed, not easy oke, will get you more users. | |
| ID: 100319 | | |
6.10.11 to be more precise ... though the .3 release was almost there ... | |
| ID: 100322 | | |
|
Just finished the first 2 WUs and from the lloks of it, they were kind of slow http://einstein.phys.uwm.edu/results.php?userid=271017 | |
| ID: 100328 | | |
|
Variable, and probably depends significantly on the speed of your CUDA card too. | |
| ID: 100330 | | |
|
11.11.2009 18:50:20 Einstein@Home Sending scheduler request: Requested by user. | |
| ID: 100413 | | |
11.11.2009 18:50:20 Einstein@Home Requesting new tasks for CPU 1. You'll have to wait for a request for GPU tasks. 2. Does your app_info.xml contain S5R6-related information? Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) ![]() | |
| ID: 100416 | | |
Don't know. It's from newly downloaded archive with cuda apps (einsteinbinary_ABP1_3.10_windows_intelx86_cuda.zip). What should be there else? | |
| ID: 100419 | | |
That zip was created before S5R6 began, so it's a bit out of date. You'd have to stop BOINC, make some updates to the app_info.xml (analogous to http://einstein.phys.uwm.edu/forum_thread.php?id=7540&nowrap=true#100336, see items highlighted in bold (don't copy and paste as that example is for Linux) and restart BOINC. Bikeman ____________ ![]() ![]() | |
| ID: 100421 | | |
|
Thanx, it started work. | |
| ID: 100428 | | |
There is currenty no CPU version in beta test anymore (they were promoted to stock app by now), so could remove that app_info.xml after fully consuming the cached work. Bikeman ____________ ![]() ![]() | |
| ID: 100430 | | |
| |
| ID: 100441 | | |
|
In fact it takes a few seconds to slow down the graphics. Seems like the memory of the GPU is getting full and the computer spend is time to swap between the GPU memory and the rest... All the graphics a terribly slow (close window, open window...) | |
| ID: 100442 | | |
Hello Kty Is it the first time you use your gpu to compute ? If yes, it will be interesting to compare your feelings on an other gpu-computing project, like seti. It is usual to have some screening slow down when gpu-computing, moreover when your card is a little one. The fact is that you sature your GPU by computing. Your solution to stop computing when user is active is a good compromise. That's what I've done on some machines. See you GuL ____________ | |
| ID: 100448 | | |
|
Hello Gul, | |
| ID: 100451 | | |
There is no automatically distributed CUDA app (yet), only a beta app you have to install manually. None of Einstein@Home tasks done on your PC lately uses the GPU. Are you really sure the lack of responsiveness on your PC is caused by E@H? Does the situation improve if you temporarily halt (suspend) all running E@H jobs, and does it go back to "slow" if you resume them? Cheers Bikeman ____________ ![]() ![]() | |
| ID: 100453 | | |
That's a good advice. Lionel --> You told you modified your einstein preferences. Do you remember what you've modified exactly ? Cheers ____________ | |
| ID: 100468 | | |
|
I Tried to use the app_info.xml from the beta page but it wouldnt run. I need entries for S5R6 and Arecibo in the file as well. | |
| ID: 100571 | | |
I Tried to use the app_info.xml from the beta page but it wouldnt run. I need entries for S5R6 and Arecibo in the file as well. Already posted (details in message 99970) | |
| ID: 100572 | | |
I Tried to use the app_info.xml from the beta page but it wouldnt run. I need entries for S5R6 and Arecibo in the file as well. Thanks, thats helped. | |
| ID: 100574 | | |
Message boards :
Cruncher's Corner :
CUDA App einsteinbinary 3.10 for Windows available for Beta Test