| log in |
Message boards : Application Code Discussion : GPU app teaser
| Author | Message |
|---|---|
|
As I already mentioned in some other posts, I am working on an implementation of the MW application on ATI graphics hardware (RV670 and up, that means HD38x0, HD4670?? and HD48x0). It is not finished yet (still some scheduling problems as BOINC only supports CUDA atm), but it calculates some results that are in line with the requirements (at least when running offline, have to ask Travis for this ones). | |
| ID: 9229 | Rating: 0 | rate:
| |
|
Holy mother of moo moo's... 8seconds per WU!! | |
| ID: 9232 | Rating: 0 | rate:
| |
|
I agree, excellent work!! | |
| ID: 9233 | Rating: 0 | rate:
| |
|
I've just had a go at knocking out my first GPU WU which recently completed giving me nearly 4,000 credits. | |
| ID: 9235 | Rating: 0 | rate:
| |
I've just had a go at knocking out my first GPU WU which recently completed giving me nearly 4,000 credits. Travis, please transfer those 4,000 credits to my account. That beats all. ____________ | |
| ID: 9244 | Rating: 0 | rate:
| |
|
Now there is the making of a conundrum ... which card to get ... ATI so you can do Milky Way or Nvida so you can do SaH and / or GPU Grid? | |
| ID: 9275 | Rating: 0 | rate:
| |
|
w00t, sign me up! Just been waiting to get my 4870 1GB rolling. I was waiting on AI because they're working on an official app last I heard, but Milkyway will work too! :-D | |
| ID: 9276 | Rating: 0 | rate:
| |
|
That's really crazy. Now I wish I had an ATI card... | |
| ID: 9290 | Rating: 0 | rate:
| |
Otherwise it's only another method to crunch more WUs without getting more credits from it. You mean, like work without pay? ____________ | |
| ID: 9291 | Rating: 0 | rate:
| |
Otherwise it's only another method to crunch more WUs without getting more credits from it. Not without pay, but close to it! With the current limits (especially the 300WU limit per core), you get only about 320 credits/day on that system with the GPU app *lol* If it is really going to work, Travis has to do something on this. | |
| ID: 9294 | Rating: 0 | rate:
| |
Not without pay, but close to it! Gulp! I can't image anyone providing computer resource to a BOINC project like this and getting almost negligible credit results in return. ____________ | |
| ID: 9296 | Rating: 0 | rate:
| |
Not without pay, but close to it! Just think of it as a small fan-heater that supplies 8k+ MW units/day when its not needed as a graphics card. | |
| ID: 9299 | Rating: 0 | rate:
| |
|
If someone has thought, the screenshot may be a fake, there is a video of the running app. | |
| ID: 9310 | Rating: 0 | rate:
| |
If someone has thought, the screenshot may be a fake, there is a video of the running app. Jeeeeeezzzz... And i thought you mean't 1 result every 10 or so seconds! But 4!! Wohay, why the hell did i get Nvidia! :P Great app! | |
| ID: 9311 | Rating: 0 | rate:
| |
Jeeeeeezzzz... And i thought you mean't 1 result every 10 or so seconds! But 4!! Wohay, why the hell did i get Nvidia! :P It's 4 WUs every 35 to 40 seconds or so. It is effectively every 9 seconds a WU. If you lower the resource share (calculate some other projects in parallel), the app will calculate less MW-WUs in parallel (you can run other projects in parallel), but the absolute troughput will stay the same (1 WU per 9 seconds). | |
| ID: 9319 | Rating: 0 | rate:
| |
w00t, sign me up! Just been waiting to get my 4870 1GB rolling. I was waiting on AI because they're working on an official app last I heard, but Milkyway will work too! :-D I have an ATI Radeon X1900 in my Mac. Two questions. 1) "...that means HD38x0, HD4670?? and HD48x0" What the heck does that mean? Which cards/chips are we talking about? 2) Will this app work on Macs? ____________ | |
| ID: 9338 | Rating: 0 | rate:
| |
Two questions. 1. Consider the x as a wildcard. It runs on RV670 and RV770 class GPUs (and anything newer supporting double precision, so it's forward compatible). That are HD 3850, HD3870, HD4850 and HD 4870 (most probably HD4830 too). As for the RV730 (HD4670 and HD4650) there is some contradicting information. It is tested not to run with the current driver, but this may or may not change with a newer driver revision. 2. Macs are not supported (you can't even download a driver for the newer cards from AMD, so I suppose they wouldn't run). But there is potential support for Linux (not implemented yet). | |
| ID: 9340 | Rating: 0 | rate:
| |
[quote] your X1900 will not work. you need at least a card with the RV670 chip (3850, 3870) or with RV770 chip (4830, 4850, 4870). In principle all ATIs starting from the RV670 should work, but sometimes the double precision is locked by either the bios or driver (4670 refused to work) | |
| ID: 9341 | Rating: 0 | rate:
| |
|
8 tasks on 1 gpu ;) | |
| ID: 9372 | Rating: 0 | rate:
| |
|
Is there any way to get the application now, or is it just open to Planet 3DNow members? | |
| ID: 9380 | Rating: 0 | rate:
| |
|
No, it's here: http://www.planet3dnow.de/vbulletin/showpost.php?p=3850506&postcount=762 click: "die neue Version (V3)" | |
| ID: 9394 | Rating: 0 | rate:
| |
No, it's here: http://www.planet3dnow.de/vbulletin/showpost.php?p=3850506&postcount=762 click: "die neue Version (V3)" Heh, that was quick. And of course, I can't actually use the application until Saturday... I'll keep an eye on this thread, and start testing as soon as I can. ____________ | |
| ID: 9398 | Rating: 0 | rate:
| |
... Pure coincidence. Good Night... @03:32 ... in Germany... | |
| ID: 9400 | Rating: 0 | rate:
| |
Is there any way to get the application now, or is it just open to Planet 3DNow members? If you browse our forum, you will find it. It's not in a somehow closed forum where you have to login or even have to be member of the team. You will find it also as a guest and now even easier as Emploi posted the link ;) But it would be helpful if you could read some German, as there are instructions in that thread (you may need to edit the included app_info.xml). It is still a test version (think of it as an alpha version or technology demonstrator, it not a release candidate yet) and some things are simply not working in the moment. I'm in contact with Travis about it as well. My plan is to give the app including the code to the project when it is working as desired and can be distributed as the stock GPU application of Milkyway. And if you are interested in your credit standings, you better not run this app with the current credit and WU limits. A quad core with a HD4870 gets only about 330 credits a day, a dual core only 165 credits or so (as the number of WUs you get scales with the number of your cores, even if the calculation speed does not depend on them). It is just the pure enthusiasm that let one lone guy run that app, not the credits. Furthermore we simply need to test it, so I'm really thankful for that (as I don't have a compatible card). | |
| ID: 9401 | Rating: 0 | rate:
| |
Is there any way to get the application now, or is it just open to Planet 3DNow members? Understood. I know it's just for testing, but it also helps to heat up the room here. :-P The only thing is I don't speak any German, but I've tweaked plenty of app_info.xml files before, so I can get it running. Is it fine if I were to just report anything I find here, or should I still get an account on Planet 3DNow's forums? ____________ | |
| ID: 9404 | Rating: 0 | rate:
| |
Understood. I know it's just for testing, but it also helps to heat up the room here. :-P The only thing is I don't speak any German, but I've tweaked plenty of app_info.xml files before, so I can get it running. Is it fine if I were to just report anything I find here, or should I still get an account on Planet 3DNow's forums? I guess it does not matter too much, you can also ask here. For starters, the content of the app_info.xml does not only decide if it runs or not, but also how it runs. With the values avg_ncpus and max_ncpus and the ncpu value of your cc_config.xml you can control (actually together with the resource share, if you run other projects at the same time) how much MW-WUs run concurrently. It will use one core, no matter how many WUs are calculated in parallel. Running two at once could give a slightly better throughput (think about saving 0.2 seconds per WU or so), running more could give diminishing returns. Especially if you set the avg_ncpus value very low, it may become slower. I would suggest setting the ncpu value of your cc_config.xml to your actual numbers of cores +1, set avg_ncpu and max_ncpu both to one and then chose the resource share of milkyway that way, that 2 WUs run concurrently. Example: Quadcore, ncpu in cc_config.xml set to 5 (calculates then 5 WUs in total parallel) and MW resource share to 2/5 = 40%. Milkyway will use then effectively one core and three are left for other things and it calculates 2 MW-WUs in parallel. You can also test a very low resource share for MW and setting the avg_ncpus in the app_info.xml to a low value (like 0.25). The slower the card, the lower you can set this before loosing too much performance. 0.2 should be the absolute minimum for a HD4870, a HD3850 may run also with 0.1 quite well. These values get really interesting if/when I release the CPU during the computation. | |
| ID: 9408 | Rating: 0 | rate:
| |
Understood. I know it's just for testing, but it also helps to heat up the room here. :-P The only thing is I don't speak any German, but I've tweaked plenty of app_info.xml files before, so I can get it running. Is it fine if I were to just report anything I find here, or should I still get an account on Planet 3DNow's forums? All right, sounds cool. Why I can't run the application right now is I blew a fuse in the power supply (not from overcurrent, it was stupidity on my part), and I'll have a new one for Saturday (tomorrow). It is indeed a quad-core: an overclocked Q6600 to be exact. So I'll try the values you suggested once that's back up. ____________ | |
| ID: 9417 | Rating: 0 | rate:
| |
|
Tested GPU app on HD3870. | |
| ID: 9432 | Rating: 0 | rate:
| |
Tested GPU app on HD3870. That's what I'm working on. I've already said some things are simply not working, yet. Do you remember the news about the new WUs with two streams in it? They can't be calculated on the GPU in the moment. The flop counting for this type of WUs is also wrong. If I find some time I will extend the GPU code a bit over the weekend. But as you have seen, nothing terrible happens, it just gets slower when the app falls back to the CPU. I'm quite happy that it works like intended. I had no idea that a new type of WU would be introduced, so I'm glad I prepared for that ;) Could you please post a link to your machine (or one or two results) with a short description of your settings (resurce share of MW, changes to the app_info.xml or cc_config.xml)? It should take a bit less than 30 seconds per WU on a 3870, right? Edit: Ahh, found it here. 25 seconds for a 3870 is okay. The difference to the 9.x seconds of the HD4870 corresponds roughly to the difference in the number of stream processors for both GPUs. The shader power was raised a factor of 2.5 between the generations (besides some other tweaks). Have you played around a bit with the settings in the app_info.xml, cc_config.xml and the resource share? By the way, it is not a fair comparison, but a HD4870 here at Milkyway is doing more double precision operations per second than a GTX280 is doing single precision operations with the CUDA application of SETI. Edit2: I see you have updated the client from 5.10.30 to 6.6.3 before running the GPU app. This should have been unnecessary as the GPU stuff in there is only for nvidia cards and is not used at all. | |
| ID: 9434 | Rating: 0 | rate:
| |
Have you played around a bit with the settings in the app_info.xml, cc_config.xml and the resource share? Thanks for your comments. Yes, I've played with app_info.xml, cc_config.xml. Since there is no way to split computing to 4 CPU tasks and n GPU tasks (none that I'm aware of), I have settled to ncpus=5 and put both avg_ncpus and max_ncpus to 1. This way GPU is fequently idle so setting avg_ncpus=0.5 will make better change for GPU to take action but may slow down CPU dealing with too many tasks. No exact measurement in CPU performance was done when Q9550 is doing 4 or 8 tasks at once. Once your GPU app is ready to other WU types, it would make more sense to play with settings and resource share in order to make GPU doing MW and let CPUs on other projects. I'm using rather outdated 5.10.30 BOINC Studio core since it has backup project(s) ability. It is still left on my SSD with original projects configuration. There is nothing really important/interesting in 6.x to upgrade dozens of hosts (no multithreading project apps available for example) and GPU support is far from bug free. 6.6.3 is a fresh install with only MW attached to play with. I may revert back to BS 5.10.30 completely. ____________ BOINC Project specifications and hardware requirements | |
| ID: 9436 | Rating: 0 | rate:
| |
|
Thank you for all your work on this. I must say it's good to hear AMD/ATI's cards are performing so well now, considering they've been playing catchup for a while (from what I can gather, anyway). Is the code very different from the CUDA equivalent? And would a CUDA conversion be worth it? (I heard the GTX280 is much better at double precision operations than earlier cards, but it sounds like even it is outmatched by current offerings by AMD) | |
| ID: 9443 | Rating: 0 | rate:
| |
Thank you for all your work on this. I must say it's good to hear AMD/ATI's cards are performing so well now, considering they've been playing catchup for a while (from what I can gather, anyway). Is the code very different from the CUDA equivalent? And would a CUDA conversion be worth it? (I heard the GTX280 is much better at double precision operations than earlier cards, but it sounds like even it is outmatched by current offerings by AMD) Like the Intel / AMD wars the ATI and Nvidia wars have first one then the other out in front... I am sure that if this application gets going here demonstrating the capabilities of the ATI cards that Nvidia will notice and respond in the next generation. And if it does prove out I can still get a couple of ATI cards to go in two of my systems though I will be Nvida heavy for a bit ... But first, we have to have the application ... :) | |
| ID: 9445 | Rating: 0 | rate:
| |
Is the code very different from the CUDA equivalent? And would a CUDA conversion be worth it? (I heard the GTX280 is much better at double precision operations than earlier cards, but it sounds like even it is outmatched by current offerings by AMD) No, the general programming principle is quite similar for ATI and nvidia. There are of course some differences how to obtain maximum performance, but luckily some of them apply only to single precision (ATI cards like vectorization, which is not required for nvidia). I really think a CUDA app would be easier to implement (their software developement kit is simply better), but with a GTX280 not able to reach the performance of a HD3850 in double precision, I don't know if it is really worth the effort. The current generation ATI hardware (RV770) has a factor 3 performance advantage over the GT200 GPUs from nvidia. nvidia made a lot of fuss about the double precision units in the GT200 (GTX2xx cards), but frankly they are quite a design flaw from the performance point of view (at least when doing pure double precision calculations). They have 240 high clocked single precision units, but only 30 double precision units (which can do even less per clock than the single units). The result is that the performance with doubles is only 1/12 of the performance with singles. On the other hand ATI has incorporated 160 5-issue VLIW units (doing up to five operations on singles). If you want to calculate with doubles, either two or four of the five 32bit subunits are combined. That means such a VLIW unit is able to produces one or two double results per clock (the 5th subunit can still be used for other things). So effectively a RV770 is able to churn out between 160 and 320 double results per clock cycle (dividing the single throughput by 5, for adds actually only by 2.5), nvidia is only able to do 30. The higher clock of the nvidia shaders won't help with the massive advantage ATI has on the number of double capable units as they use the same ones for singles and doubles. The GPU part of the MW code does close to 150 GFlop per second on a HD4870. Averaged over the whole runtime (a little bit is still calculated on the CPU and you have some overhead, like transfering data to the GPU and so on) it is more than 130 GFlop/s. The theoretical peak performance of a GTX280 is only 78 GFlop/s with doubles. I wouldn't expect more than 50 GFlop/s from a GTX280 on the MW code. So maybe a triple SLI system is as fast as a single HD4870. And a high clocked Core i7 also does already about 35 GFlop/s (~61 GFlop/s Peak at 3.8GHz). | |
| ID: 9465 | Rating: 0 | rate:
| |
|
Got some errors with the workunits. I made the mistake of setting the app in, then putting Milkyway wide open. About 7 tasks quit with an error before I suspended the rest. Looking in one of the reported WUs, the exit code is 0xc0000135. Googling for that returns many results for BOINC, most of which seem to say it's a missing DLL. I'm presuming this to be brook.dll. So maybe the app_info has to be tweaked so it's also copied to the slots directory? I'm not sure how to verify what files are in there to check, as BOINC deletes them too quickly for me. | |
| ID: 9504 | Rating: 0 | rate:
| |
|
Quick notes: | |
| ID: 9510 | Rating: 0 | rate:
| |
Got some errors with the workunits. I made the mistake of setting the app in, then putting Milkyway wide open. About 7 tasks quit with an error before I suspended the rest. Looking in one of the reported WUs, the exit code is 0xc0000135. Googling for that returns many results for BOINC, most of which seem to say it's a missing DLL. I'm presuming this to be brook.dll. So maybe the app_info has to be tweaked so it's also copied to the slots directory? I'm not sure how to verify what files are in there to check, as BOINC deletes them too quickly for me. Hmm, what have you downloaded? The brook.dll is supplied in the zip file and also correctly set up in the also supplied app_info.xml. Just copy all 3 files to your Milkyway folder (and completely quit BOINC before). But maybe you need to download new WUs, as for the ones you already have there could be some issues with the data in the client_state.xml. @ the guys, where it runs, had you similiar problems? | |
| ID: 9513 | Rating: 0 | rate:
| |
Quick notes: The lagging gets better with faster cards. And don't start GPU-Z! At least under Vista64 it leads to short (two second) freezes and even some crashed WUs. Have no idea why. The CPU part is just the failsafe backup solution for the longer two-stream WUs, so it isn't the fastest version one could run ;) | |
| ID: 9514 | Rating: 0 | rate:
| |
|
So where is the link to the zip file?? Sorry in reply to Message 9513 | |
| ID: 9515 | Rating: 0 | rate:
| |
So where is the link to the zip file?? Sorry in reply to Message 9513 here http://www.file-upload.net/download-1414247/Milkyway_0.16_GPU_SSE3_x64.zip.html | |
| ID: 9517 | Rating: 0 | rate:
| |
So where is the link to the zip file?? Sorry in reply to Message 9513 Reading the thread helps, it's here. And remember, Win64 only, ATI HD38x0 or HD48x0 with Cat 8.12 or Cat 9.1 required. Application is in some kind of alpha state, expect some bugs, tweaking of app_info.xml and cc_config.xml may be required for optimal performance. And don't be disappointed by the credits ;) | |
| ID: 9518 | Rating: 0 | rate:
| |
@ the guys, where it runs, had you similiar problems? Well, I had some issues but not app related. Running under Win 2008 with Catalyst 8.12, automatic regulation of fan speed is not working on my HD3870. It was set to ~20% which cause GPU to overheat under full load. Driver stopped responding, W2K8 was able to recover without crashing but some WUs trashed of course. Running ATI Tray Tool and setting fan speed to 40-50% helped was good solution. I'm able to monitor GPU load, temps and fan speed with ATT without problems. In general, app is working just fine (with comments in Message 9432). ____________ BOINC Project specifications and hardware requirements | |
| ID: 9519 | Rating: 0 | rate:
| |
|
I installed it this morning on a vista 64 i7 with ati hd 4800, and they've been cranking out fine since. the short ones are running 5 - 9 seconds; the longer apps are running just shy of 10 minutes each. | |
| ID: 9521 | Rating: 0 | rate:
| |
Got some errors with the workunits. I made the mistake of setting the app in, then putting Milkyway wide open. About 7 tasks quit with an error before I suspended the rest. Looking in one of the reported WUs, the exit code is 0xc0000135. Googling for that returns many results for BOINC, most of which seem to say it's a missing DLL. I'm presuming this to be brook.dll. So maybe the app_info has to be tweaked so it's also copied to the slots directory? I'm not sure how to verify what files are in there to check, as BOINC deletes them too quickly for me. The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. ____________ | |
| ID: 9524 | Rating: 0 | rate:
| |
* ~20s GPU crunch times on i920@3.5 + 3850/256. What just comes to my mind is that the app uses about 20 MB of the video RAM per concurrent WU (actually 10 MB plus 10 MB for every stream, so in case of two streams it will be 30 MB). With an i7 (8 virtual CPUs) and the default entries in the app_info.xml it will run 16 WUs at once if you are only connected to MW. 16 * 20MB = 320MB, what is more than what you have on your card. Have you tested what happens in that case? It would have to be exclusively the short WUs, as the long (multi stream) ones are calculated on the CPU until I extend the app. In the moment I don't test how much video RAM ist still free before I allocate it. There is no error checking for the case something goes wrong. I have not thought of the 256MB variants and 512MB are enough for any sensible amount of concurrent WUs, but it would be interesting to see what happens, just in case. | |
| ID: 9526 | Rating: 0 | rate:
| |
The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. You may try to delete the line with <api_version> in the app_info.xml, but actually it should even run with the old 5.x.x clients. Remember that you have to stop BOINC also for editing the app_info.xml. | |
| ID: 9527 | Rating: 0 | rate:
| |
The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. It runs on 5.10.30 as well. ____________ BOINC Project specifications and hardware requirements | |
| ID: 9528 | Rating: 0 | rate:
| |
The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. Yes, I know I have to stop BOINC. I'll try deleting the API version line, and try again. EDIT: Same result. The hosts tasks are here if you want to look over them. ____________ | |
| ID: 9529 | Rating: 0 | rate:
| |
The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. I googled a bit and it appears you may need the .NET framework installed. Thought I've unchecked that option in the compiler (it's not used either way), but who knows. Edit: Hmm, but normally one needs the .NET framework 2.0 either way for the Catalyst driver, isn't it? Edit2: Has anyone tried the new Cat 9.1? It shouldn't make a difference, as the CAL compiler (part of the driver) still generates the same binary code to run on the GPU. | |
| ID: 9530 | Rating: 0 | rate:
| |
The files are there, and the only thing I've tweaked in the app_info is the avg_ncpus to 1. However, could it be caused by an older version of BOINC? I'm running 6.2.19. I don't know about .NET for Catalyst, but I'm running Windows 7 beta x64. It should have .NET already installed, same version as or later than Vista. As for drivers, no I haven't tried 9.1. 8.12 is all that's available for Win7 for now. ____________ | |
| ID: 9531 | Rating: 0 | rate:
| |
I don't know about .NET for Catalyst, but I'm running Windows 7 beta x64. It should have .NET already installed, same version as or later than Vista. As for drivers, no I haven't tried 9.1. 8.12 is all that's available for Win7 for now. Well, what's good for Vista (and server 2008) should be good for Win 7 (and server 2008 R2). Including drivers like Catalyst. Win 7 should be shipped with .NET 2 (server 2008 and 2008 R2 comes with it). It has both x86 and x64 .NET 2 version in it. Anyway, if you installed (full) Catalyst, CCC (Catalyst Control Center) needs .NET. If it's working, means you have .NET 2 working. ____________ BOINC Project specifications and hardware requirements | |
| ID: 9532 | Rating: 0 | rate:
| |
...I have not thought of the 256MB variants and 512MB are enough for any sensible amount of concurrent WUs, but it would be interesting to see what happens, just in case. On my system the WUs "stalls" when more than 6 WU are run concurrently, ie the CPU and GPU usage goes to 0%. Restarting Boinc manager solves the problem for a while then it just stalls again. | |
| ID: 9538 | Rating: 0 | rate:
| |
|
As stated 4670 does not seem to be working this is an MSI 4670 512 MB | |
| ID: 9541 | Rating: 0 | rate:
| |
...I have not thought of the 256MB variants and 512MB are enough for any sensible amount of concurrent WUs, but it would be interesting to see what happens, just in case. It appears it needs double the graphics memory I thought, about 40MB per WU. That would explain your findings. | |
| ID: 9542 | Rating: 0 | rate:
| |
As stated 4670 does not seem to be working this is an MSI 4670 512 MB There are actually two reasons why it is not working. A HD4670 does not support double precision (only HD38x0 and HD48x0) and the app is a 64Bit application. So one needs a WinXP64, Vista64, Server 2003 x64, Server 2008 or a Windows7 installation (maybe I forgot something), but it is not running on WinXP Pro SP3. | |
| ID: 9544 | Rating: 0 | rate:
| |
|
Thank you kindly for the info and the link... Lets hope it works out maybe someone wil do an app for w32 and xseries ATI cards.. | |
| ID: 9551 | Rating: 0 | rate:
| |
|
Any more suggestions on what I should do to test the GPU app? I have a Vista x64 installation I can try with to, if that might help. | |
| ID: 9649 | Rating: 0 | rate:
| |
|
Works perfect here on a Q6600 with HD4870 running on Vista X64. Should get the label "release candidate" imho. | |
| ID: 9682 | Rating: 0 | rate:
| |
Works perfect here on a Q6600 with HD4870 running on Vista X64. Should get the label "release candidate" imho. As long the app does not handle WUs with more than one stream (still fighting some bugs of the Stream SDK to get it running) and there is no Linux variant of it, I would call it more a technology demonstrator than a release candidate. Two further things still missing are the multi GPU Support (a single HD4870 is already that fast, maybe I should restrict it to one GPU ;) and the release of the CPU during the GPU computations. But I think one could make a public beta, if the worst things are ironed out. | |
| ID: 9688 | Rating: 0 | rate:
| |
|
I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future! | |
| ID: 9746 | Rating: 0 | rate:
| |
Running ATI Tray Tool and setting fan speed to 40-50% helped was good solution. Just a short note to the GPU-Z problem also seen in the first video in this thread. It appears that not only GPU-Z but also the Catalyst control panel (if started) leads to severe lags. In case of GPU-Z it is caused by the monitoring (load, temperature, fan speed) part, the same could also apply to the CCP. But according to Honzas comment the monitoring works flawlessly with the ATI tray tools, so maybe there is some strange thing going on here. | |
| ID: 9827 | Rating: 0 | rate:
| |
|
So triple 4870's are out of the question for now I see :) | |
| ID: 10070 | Rating: 0 | rate:
| |
So triple 4870's are out of the question for now I see :) But the good thing is that a single HD4870 has almost the speed of a triple GTX280 system here at MW :D I just imagine what quad HD4870X2 system would be capable of (if one finds an appropriate power supply). That wouldn't be pretty anymore ;) Let's hope nvidia improves their double precision performance for their next generation, ATI won't get slower. | |
| ID: 10085 | Rating: 0 | rate:
| |
I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future! Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point. ____________ | |
| ID: 10204 | Rating: 0 | rate:
| |
I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future! Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again. EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how? ____________ | |
| ID: 10206 | Rating: 0 | rate:
| |
I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future! Could you post the content of the stderr.txt (shown under task details) please? I have not found it in your host list (already purged?). If "No compatible GPU found!" is the only error there, the app does not find the CAL (Compute Abstraction Layer) libraries, which are installed as part of the driver since 8.12. If the libs would be there and one has an unsupported card, it would tell you something about double precision not supported. The error you are seeing hints at an incorrectly installed or too old driver. The alternative would be a missing brook.dll, but I guess you checked that already. Or are you trying to run it when accessing the machine via a remote desktop connection? That is also not working, because Win uses some kind of a virtual framebuffer driver for that (you don't have the Catalyst as display driver in a remote session). You could use VNC and check "disable mirror driver". | |
| ID: 10209 | Rating: 0 | rate:
| |
Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again. I'll have to run another WU or two to get another stderr, but other than the XML formatting and the error code, that's all that was there. Like I said, it was a fresh install of Cat 9.1 straight off ATI's website, and the only thing I deselected during installation were the Catalyst Registration and the WoW trial. Is there any way I can find out manually if I have the CAL libraries installed? ____________ | |
| ID: 10216 | Rating: 0 | rate:
| |
Is there any way I can find out manually if I have the CAL libraries installed? Look into the Windows\system32 folder. There should be the files "amdcalcl64.dll", "amdcaldd64.dll" and "amdcalrt64.dll". | |
| ID: 10218 | Rating: 0 | rate:
| |
Is there any way I can find out manually if I have the CAL libraries installed? Well, that explains some stuff... They don't exist in the Win7 installation, but they do in the Vista installation. So it does seem Catalyst for Win7 doesn't have Stream support yet. Still doesn't explain why Vista fails. ____________ | |
| ID: 10219 | Rating: 0 | rate:
| |
|
I've been using the gpu app for almost 2 weeks now and just wanted to give a little feedback. I've rolled back my driver to the 8.12 version from 9.1 yesterday. I was running 8.12 fine but wanted to get the latest driver installed when it came out. After the upgrade i had a lot of pc responsiveness issues and a bsod every few days. Since then my computer has ran much smoother. I'm not sure why the newer driver just didn't seem to perform as well as 8.12. I should mention i'm running gpu version 0.17. | |
| ID: 10515 | Rating: 0 | rate:
| |
I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future! Hi, Same problem for me with Vista64 + Catalyst 9.1 <core_client_version>6.2.19</core_client_version> <![CDATA[ <message> Fonction incorrecte. (0x1) - exit code 1 (0x1) </message> <stderr_txt> No compatible GPU found! </stderr_txt> ]]> | |
| ID: 10642 | Rating: 0 | rate:
| |
The screenshot and two videos posted in this thread are done on Vista64. There are quite some people where it runs. So please check again the points already mentioned here in the forum: - driver correctly installed (three amdcal??64.dll files present in Windows/system32 folder) - you are not accessing the machine over a remote desktop connection (use VNC and disable mirror driver) - the card should be active (monitor connected to it) | |
| ID: 10649 | Rating: 0 | rate:
| |
|
Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo). | |
| ID: 10651 | Rating: 0 | rate:
| |
Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo). Thanks for the feedback on the Vista64 issue. The credits you get are less than a Quadore with an optimized CPU app gets (432credits/hour). Furthrmore you can't let it run for 24h a day. After about 6 hours you have used up your WU limit of 1000 WUs per day and core and that will earn you less than 2000 credits a day. So you should definitely run another project at the same time. The MW GPU app uses only one core no matter how many WUs run concurrently. The work done for MW won't change, if you run it only with 50% resource share (2 WUs at the same time). Just try it! | |
| ID: 10652 | Rating: 0 | rate:
| |
Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo). Thank you very much for this information ^^ I tried a few hours ago to (re)join my main project (World Community Grid), but I stopped when I saw "only" two MW workunits instead of 4 before ^^ But the 1000 Wu limit per day change everything ^^ Question : if the GPU app uses only one core, is it possible to use the other core for a CPU-optimized app ? Or use all the cores with the GPU ? ____________ Star Wars BOINC Team | |
| ID: 10654 | Rating: 0 | rate:
| |
- driver installed yesterday, the 3 files are in System32 (amdcalcl64.dll ,amdcaldd64.dll and amdcalrt64.dll) - i didn't use any remote protocol, it's my main PC - the card was active, there is only one. | |
| ID: 10659 | Rating: 0 | rate:
| |
|
How have you guys installed the BOINC client? | |
| ID: 10664 | Rating: 0 | rate:
| |
How have you guys installed the BOINC client? Default options for me on Vista64, so I think I used the protected mode. It worked very fine until the 2000 WU limit. I earned 1939 credits in 6 hours. Only three WU went wrong during the initial tests, but it was my fault ^^ | |
| ID: 10682 | Rating: 0 | rate:
| |
How have you guys installed the BOINC client? Hmm, that makes sense... I think I did a service install, which would be that. Unfortunately, I won't have access to the machine for at least a week, so I can't test what the other install would do. I can try it after I have access again though. ____________ | |
| ID: 10692 | Rating: 0 | rate:
| |
How have you guys installed the BOINC client? I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support | |
| ID: 10827 | Rating: 0 | rate:
| |
I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support Isn't the default the protected mode? The experience of some users indicate the lags or short (one or two seconds) freezes are caused by either GPU-Z or the Catalyst Control Center. If these tools are closed it normalizes within a minute or so. | |
| ID: 10839 | Rating: 0 | rate:
| |
|
Probably silly question, but, Why can these certain graphics cards do their own work for projects and not older cards? | |
| ID: 10915 | Rating: 0 | rate:
| |
Probably silly question, but, Why can these certain graphics cards do their own work for projects and not older cards? Because the older cards can only do single precision calculations (32bit) and the HD38x0 and HD48x0 are the only ones (besides nvidias GTX2xx series) that can handle double precision (64bit). | |
| ID: 10929 | Rating: 0 | rate:
| |
I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support No, per default the protection mode is off, you have to choose the "Protected application execution" option separately. ____________ Lovely greetings, Cori | |
| ID: 10931 | Rating: 0 | rate:
| |
I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support Oh, I guess they have changed it because of the CUDA apps for SETI *lol* | |
| ID: 10932 | Rating: 0 | rate:
| |
I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support Hehe, I think it was disabled for default from the very beginning. I've tried it once when it was newly added and it didn't convince me too much. *grin* So I was glad I didn't have to un-check that option everytime I upgraded BOINC. :-D ____________ Lovely greetings, Cori | |
| ID: 10933 | Rating: 0 | rate:
| |
|
Sorry to sound stupid but is a 9700 all in one wonder to old to use this application? | |
| ID: 10934 | Rating: 0 | rate:
| |
Sorry to sound stupid but is a 9700 all in one wonder to old to use this application? Sorry, but some years too old. | |
| ID: 10937 | Rating: 0 | rate:
| |
Probably silly question, but, Why can these certain graphics cards do their own work for projects and not older cards? Isn't that what pc's do? But older cards could do single calc's then. Why not add support for those? There would be plenty, since these new cards aren't that old. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 10944 | Rating: 0 | rate:
| |
Sorry to sound stupid but is a 9700 all in one wonder to old to use this application? No worries. Thanks for the swift reply. | |
| ID: 10945 | Rating: 0 | rate:
| |
Probably silly question, but, Why can these certain graphics cards do their own work for projects and not older cards? This is about the floating point precision. Travis has set quite strict limits for the reslts of the test WUs. You can't reach them with single precision calculations on older cards (the really old ones support only 16 or 24bit FP). It may be possible to get there with some kind of software emulation, but this would be a lot of effort which would be lost in the future as more and more cards get double precision support. Furthermore it would be most likely as slow ;) or even slower than to do the computations on a CPU. | |
| ID: 10949 | Rating: 0 | rate:
| |
Ok. I guess if it was worth it, other projects would be using it for the 'older' cards. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 10951 | Rating: 0 | rate:
| |
Ok. I guess if it was worth it, other projects would be using it for the 'older' cards. Don't forget for most other projects (like SETI or GPUGrid) single precision is enough. That is the reason you can also use slightly older cards there. MW is just more demanding in this specific area. | |
| ID: 10954 | Rating: 0 | rate:
| |
Ok. I guess if it was worth it, other projects would be using it for the 'older' cards. I haven't seen much mention of their use till recently. Though I haven't checked the other projects boards. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 10955 | Rating: 0 | rate:
| |
|
Running pretty well on my HD4830, but I would like it to be running 2 wu's instead of the 8 or so it's running currently. I have played with the app_info file and so far have had no success. Right now it's set on avg_ncpus to 0.2, and max_ncpus to 5 (quad core intel). Resource share on MW is set to 10% and it still continues to run 10 wu's in parallel. Any suggestions? | |
| ID: 10971 | Rating: 0 | rate:
| |
Running pretty well on my HD4830, but I would like it to be running 2 wu's instead of the 8 or so it's running currently. I have played with the app_info file and so far have had no success. Right now it's set on avg_ncpus to 0.2, and max_ncpus to 5 (quad core intel). Resource share on MW is set to 10% and it still continues to run 10 wu's in parallel. Any suggestions? I think I got it, but man it is killing my screen response time! | |
| ID: 10973 | Rating: 0 | rate:
| |
Running pretty well on my HD4830, but I would like it to be running 2 wu's instead of the 8 or so it's running currently. I have played with the app_info file and so far have had no success. Right now it's set on avg_ncpus to 0.2, and max_ncpus to 5 (quad core intel). Resource share on MW is set to 10% and it still continues to run 10 wu's in parallel. Any suggestions? Increase avg_ncpus and run another project at the same time. The screen response is far better, if you close GPU-Z and the Catalyst Control Center (and probably some other tools with monitoring functions). It appears there is some interaction with the monitoring stuff in these. But some tools are checked to be running fine in parallel, afaik ATI Tray Tools and Everest. | |
| ID: 10976 | Rating: 0 | rate:
| |
|
I am running another project, and I switched the resource share to 40% here at MW, bumped the avg_ncpus up to 0.5. I closed CCC and it seemed to help a bit, more towards the acceptable level. | |
| ID: 10981 | Rating: 0 | rate:
| |
|
avg_ncpus set to 0.1 | |
| ID: 11007 | Rating: 0 | rate:
| |
avg_ncpus set to 0.1 I'm working on something to remove the credit limit, which should go live in the next couple days. Also, I can raise the workunit-per-cpu limit. What would be a good value? ____________ | |
| ID: 11008 | Rating: 0 | rate:
| |
Also, I can raise the workunit-per-cpu limit. What would be a good value? 3600*24/9 is up to ~10K WUs per day on HD4870. Too bad BOINC is still far from ready for GPUs. I would have suggested to raise WU limit only for hosts with GPUs and distribute WUs with pretty short deadline or extra large ones for such hosts... ____________ BOINC Project specifications and hardware requirements | |
| ID: 11017 | Rating: 0 | rate:
| |
Also, I can raise the workunit-per-cpu limit. What would be a good value? I think one of the recent updates to the BOINC server code allows for a separate daily WU queue for GPUs. I'll do a little looking into it and if thats the case then we can give the GPUs a 10k daily limit without touching the other one. ____________ | |
| ID: 11018 | Rating: 0 | rate:
| |
|
Sounds like a good idea to me. | |
| ID: 11019 | Rating: 0 | rate:
| |
I think one of the recent updates to the BOINC server code allows for a separate daily WU queue for GPUs.Well, it may (i don't know). But I known that even latest BOINC client 6.6.7 still doesn't recognize GPUs (means both nVidia and ATI/AMD GPUs), only CUDA capable devices. (not only) MW would benefit a lot from support of ATI GPUs under BOINC, especially those capable of double precision... ____________ BOINC Project specifications and hardware requirements | |
| ID: 11023 | Rating: 0 | rate:
| |
avg_ncpus set to 0.1 You should not set max_ncpus to another value than exactly 1. It is the maximal number of cores a single WU can use. As the app is single threaded it can't use more than a core. That the WUs are taking the same time no matter how many WUs are running concurrently is perfectly normal. There is probably a slight increase in efficiency (maybe 5%) if two WUs are running compared to a single one. The reason is that you can carry out the few calculations still necessary on the CPU in the time when another WU is waiting for the GPU. But more than two WUs won't help more (but don't hurt either). You will have a throughput of about one WU per 9.x seconds either way on a HD4870. But there is a limit on the number of concurrent WUs. If you try to run more than 12-16 (~30) WUs on a 512MB (1GB) card, it starts to get slower and finally breaks, because there is not enough memory on the card. In the moment there is no mechanism to check for available RAM on the card. You shouldn't set avg_cpus to very low values to avoid this situation. PS: I guess the credit situation gets better if the limits are lifted by Travis ;) | |
| ID: 11024 | Rating: 0 | rate:
| |
I think you need to make sure that there is plenty of work to do if many of these are ran. Might be time for server #2. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 11031 | Rating: 0 | rate:
| |
|
max_ncpus back to "1". | |
| ID: 11038 | Rating: 0 | rate:
| |
max_ncpus back to "1". With the gpu, I can crunch 16 @ a time with the i7, so 10k limit per core, or 80,000 in my case, would be a more realistic than 4000. | |
| ID: 11041 | Rating: 0 | rate:
| |
Cluster > If I understand correctly, your optimization uses "only" one core at a time, is that right ? Is it possible to use more core, so we can use only Milkyway on one computer with more than one core ? The goal is actually to use not a full core (or even more), but maybe only 10% of a core or so. This way your CPU would be free to crunch something else. If it is really wanted I could put in support for simultaneous crunching of MW on GPU and CPU. But this would have a low priority on my list. | |
| ID: 11055 | Rating: 0 | rate:
| |
With the gpu, I can crunch 16 @ a time with the i7, so 10k limit per core, or 80,000 in my case, would be a more realistic than 4000. But the throughput is still be one WU every 9 seconds or so with a HD4870. It is not getting faster with more concurrent WUs. So with a HD4870 a limit of 10,000 WUs a day would be enough as long there is no multi GPU support implemented (or massive overclocking involved). I would say 10,000 WUs per host and day are needed now. When multiple cards are working and/or newer GPUs are available, this needs to be raised again. | |
| ID: 11057 | Rating: 0 | rate:
| |
Cluster > If I understand correctly, your optimization uses "only" one core at a time, is that right ? Is it possible to use more core, so we can use only Milkyway on one computer with more than one core ? What I would like to see is the ability to use my Nvidia in MW. I know you are using an ATI since it is faster, but I only have the Nvidia which I'd be interested in transferring from crunching on GPUGRID to MW. ____________ | |
| ID: 11058 | Rating: 0 | rate:
| |
Cluster > If I understand correctly, your optimization uses "only" one core at a time, is that right ? Is it possible to use more core, so we can use only Milkyway on one computer with more than one core ? Afaik, there is already a student starting to work on a CUDA app. As this is easier to work with, I guess we could see some results soon ;) But don't expect times much below 25s per WU for nvidias GTX line. And older ones won't work at all (lack of double precision units). | |
| ID: 11060 | Rating: 0 | rate:
| |
What I would like to see is the ability to use my Nvidia in MW. I know you are using an ATI since it is faster, but I only have the Nvidia which I'd be interested in transferring from crunching on GPUGRID to MW. 25 secs? Blimey, hurry up student :) ____________ | |
| ID: 11061 | Rating: 0 | rate:
| |
25 secs? Blimey, hurry up student :) But that is soooo slooooow compared to the less than 10 seconds on ATIs HD4870 ;) | |
| ID: 11064 | Rating: 0 | rate:
| |
25 secs? Blimey, hurry up student :) 25 sec is good enough for me, hurry up student :-) | |
| ID: 11067 | Rating: 0 | rate:
| |
25 secs? Blimey, hurry up student :) Rats, I need a new graphics card finally! ____________ Lovely greetings, Cori | |
| ID: 11068 | Rating: 0 | rate:
| |
With the gpu, I can crunch 16 @ a time with the i7, so 10k limit per core, or 80,000 in my case, would be a more realistic than 4000. oh, i agree with that too. the turn around time for the gpu app was about 2 1/2 minutes. i've been running the op app this week and it's crunching 8 wu's in 6 minutes since the .19's came out, so that limit needs to go much higher as well. | |
| ID: 11081 | Rating: 0 | rate:
| |
With the gpu, I can crunch 16 @ a time with the i7, so 10k limit per core, or 80,000 in my case, would be a more realistic than 4000. It should be enough for your i7, as the current limit is 1,000 WUs per day and core/thread. That means on your i7 you have actually 8,000 WUs a day to play with. You won't come close to that limit with the CPU alone, but it will last for 21 hours a day only on the GPU ;) | |
| ID: 11087 | Rating: 0 | rate:
| |
Cluster > If I understand correctly, your optimization uses "only" one core at a time, is that right ? Is it possible to use more core, so we can use only Milkyway on one computer with more than one core ? Yeah hopefully within the next week or two we'll have an alpha CUDA application for you guys to crash :D ____________ | |
| ID: 11101 | Rating: 0 | rate:
| |
Yeah hopefully within the next week or two we'll have an alpha CUDA application for you guys to crash :D Well, I have one GTX 280 and 2 GTX 295s ... start your engines ... Of course we will need a setting on the site to get only CPU work, only CUDA work ... or both ... | |
| ID: 11116 | Rating: 0 | rate:
| |
Yeah hopefully within the next week or two we'll have an alpha CUDA application for you guys to crash :D It's effectively important to have both options. ____________ | |
| ID: 11132 | Rating: 0 | rate:
| |
Yeah hopefully within the next week or two we'll have an alpha CUDA application for you guys to crash :D I'm hoping that eventually we can get an OpenCL implementation that will work on both ATI and Nvidia cards... we'll see how that whole thing pans out :P ____________ | |
| ID: 11138 | Rating: 0 | rate:
| |
|
My HD4830 times have been going up steadily in the last day or so. Running almost 30 seconds now. | |
| ID: 11166 | Rating: 0 | rate:
| |
My HD4830 times have been going up steadily in the last day or so. Running almost 30 seconds now. There are quite some dual stream work units out there. They take about 50% longer but are also giving 50% more credits (~ 18.5 credits). I would say your crunch times appear to be completely okay. | |
| ID: 11173 | Rating: 0 | rate:
| |
|
Awesome, thank you for all your help. | |
| ID: 11175 | Rating: 0 | rate:
| |
Awesome, thank you for all your help. It won't help as the MW app is single threaded and it may have the negative side effect of blocking other applications to run concurrently. So I would leave it at 1. And don't take the CPU time you see too serious. Now, with the disappered credit limit it doesn't matter anyhow. The important thing is just the throughput, i.e. how many WUs are you crunching per minute/hour/day wall clock time. | |
| ID: 11185 | Rating: 0 | rate:
| |
|
How big of an impact does amount of memory on the card (ie 512MB vs 1GB 4870) have on crunch times? | |
| ID: 11188 | Rating: 0 | rate:
| |
How big of an impact does amount of memory on the card (ie 512MB vs 1GB 4870) have on crunch times? None. Also the speed of the memory does not have a pronounced effect (cache hit rates are quite high). The advantage of a HD4870 compared to a HD4850 stems only from the higher clockrate (+20%). The almost doubled memory bandwidth of the HD4870 (GDDR5 vs GDDR3) does not help in case of MW. The algorithm is dominated by computations, not memory accesses. One has only one memory access every eleven instructions or so. And as most of these accesses can be cached quite well it doesn't need much memory bandwidth. Actually it is the same behaviour as one sees with the CPU version. More memory on the card would only enable the possibility to crunch more WUs concurrently (think of 30+ on a 1 GB card). But as more WUs in flight does not help the througput, it is only an esoterical advantage. | |
| ID: 11203 | Rating: 0 | rate:
| |
How big of an impact does amount of memory on the card (ie 512MB vs 1GB 4870) have on crunch times? Interesting- thanks for that info... ummm, 32 bit XP version in the works?? ;) | |
| ID: 11216 | Rating: 0 | rate:
| |
32 bit XP version in the works?? ;) Will be the next thing I do. It's now a higher priority than to fiddle around with multi GPU or linux support. | |
| ID: 11246 | Rating: 0 | rate:
| |
|
Regarding Multi-GPU: does that mean that at the moment you can run only GPU or only one card per PC ? What should one look for: an 4870X2 or an 4870 ? | |
| ID: 11263 | Rating: 0 | rate:
| |
Regarding Multi-GPU: does that mean that at the moment you can run only GPU or only one card per PC ? What should one look for: an 4870X2 or an 4870 ? In the moment it uses only one GPU per machine. I hope I can extend it to arbitrary values in the future. Just have to find some time (and two cards to test) for it ;) | |
| ID: 11266 | Rating: 0 | rate:
| |
|
Thanx, that did save me some money... :) | |
| ID: 11353 | Rating: 0 | rate:
| |
|
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". | |
| ID: 11369 | Rating: 0 | rate:
| |
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". I guess nvidias marketing has done its job ;) | |
| ID: 11371 | Rating: 0 | rate:
| |
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". lol. They probably want to change that :) ____________ | |
| ID: 11380 | Rating: 0 | rate:
| |
|
So is there currently a WU/credit limit on the GPU app, and if so, what is it? | |
| ID: 11384 | Rating: 0 | rate:
| |
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". Haha, sorry about that. I'll get it changed later today when I can get to the site(s). I meant to put 'gpu' not 'cuda'. ____________ | |
| ID: 11396 | Rating: 0 | rate:
| |
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". Might want to put ATI because I think it will only work for certain ATI cards. You might want to mention which ones as well. ____________ | |
| ID: 11398 | Rating: 0 | rate:
| |
I noticed something strange of the website (zslip.com) : the link for the ATI GPU app is labeled "Windows optimized apps (0.17 - latest, cuda)". Yes, you are right. It needs to be differentiated from the 'general' Windows versions. I'll probably put the whole info; Windows optimized apps (0.17 - latest, Win64 GPU app for ATI HD38x0 or HD48x0 card and Catalyst 8.12 or 9.1 driver) ____________ | |
| ID: 11399 | Rating: 0 | rate:
| |
|
It's my personal opinion, but I think that a full list of compatible GPUs might be great, because I can read here and there some questions about the compatibility of cards. Maybe the label "HD38x0 or HD48x0" isn't clear for all people. Maybe something like this : | |
| ID: 11410 | Rating: 0 | rate:
| |
It's my personal opinion, but I think that a full list of compatible GPUs might be great, because I can read here and there some questions about the compatibility of cards. Maybe the label "HD38x0 or HD48x0" isn't clear for all people. Maybe something like this : If you do that, and it's in these MW forums, I'd be happy to link zslip to reference it. ____________ | |
| ID: 11414 | Rating: 0 | rate:
| |
|
You can take a look (it's an alpha version ^^) : | |
| ID: 11428 | Rating: 0 | rate:
| |
You can take a look (it's an alpha version ^^) : Well, it's certainly a well laid out table and easy to read. I'm always pleased to take advantages of improvements, so if you're serious in that I can use the code for your table, I might just do that. Thanks ;) ____________ | |
| ID: 11433 | Rating: 0 | rate:
| |
http://www.starwars-holonet.com/boinc/mw.html I like that :) edit made it clickable | |
| ID: 11435 | Rating: 0 | rate:
| |
I'm serious. It took me 5 or 10 minutes to do that, so it's not a big work ^^ Take everything you want. If you want me to do something else, do not hesitate ^^ (exarkun_AT_free.fr if you want to talk more about it)
Thank you ^^ ____________ Star Wars BOINC Team | |
| ID: 11437 | Rating: 0 | rate:
| |
What can I have? ;P ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 11438 | Rating: 0 | rate:
| |
What can I have? ;P Everything from line 1 to 146 lol ____________ Star Wars BOINC Team | |
| ID: 11440 | Rating: 0 | rate:
| |
Many thanks for that Exar Kun. I have imported your code into zslip.com and tweaked it just a little bit. I think it's a great improvement - thanks ;) ____________ | |
| ID: 11475 | Rating: 0 | rate:
| |
Many thanks for that Exar Kun. I have imported your code into zslip.com and tweaked it just a little bit. You should mention cat /proc/cpuinfo for the linux CPU capabilities. Good suggestion Exar Kun and well done Ice for implementing it | |
| ID: 11482 | Rating: 0 | rate:
| |
You should mention cat /proc/cpuinfo for the linux CPU capabilities. I certainly will do, but preferably by linking to that information here. If it's posted here in MW I'll add it to zslip or link back to here as appropriate. ____________ | |
| ID: 11498 | Rating: 0 | rate:
| |
|
@ Cluster Physik: | |
| ID: 11510 | Rating: 0 | rate:
| |
Does CPU speed matter in re: to GPU application? or does GPU app not have any significant dependency on CPU? Would one expect a major difference running Pent D or AMD X2 for example vs. a Core2 CPU? As not the whole computation is done on the GPU (just 99.5% or so) it may have a small effect. But I would say it is less than one second difference per WU between a P4 and a Core2 for instance. Quite a bit of this CPU computation time can be hidden when running 2 WUs (or more) concurrently. When one WU waits some milliseconds for the GPU to complete the current task, another WU can calculate its CPU part. That's actually the reason I've integrated the possibility to run several WUs concurrently. It slightly increases the efficency. For slower CPUs it just pays off more. | |
| ID: 11512 | Rating: 0 | rate:
| |
Does CPU speed matter in re: to GPU application? or does GPU app not have any significant dependency on CPU? Would one expect a major difference running Pent D or AMD X2 for example vs. a Core2 CPU? Thanks for answering my question. Excellent! Also...this is good news as I have a PentD 945 & ECS C19A MB that are brand new, but it never seemed worth building after Core2 came out.....until now. Just need to add an ATI 4850, load-up xp64 Professional & it will have a legitimate new purpose. Cool! Edit: Last question. How many WUs can a card run w/o any performance degredation w/ 512MB GPU memory? I understand throughput remains the same untimately, but I'd be inclined to run a greater # of WUs vs. individually if there's not a performance penalty. ____________ | |
| ID: 11549 | Rating: 0 | rate:
| |
|
When can we expect a 32-bit version? I'm so excited! :D | |
| ID: 11562 | Rating: 0 | rate:
| |
|
Aha, I fixed my Issue, turns out my CCC was slightly corrupted. A reinstallation fixed it. | |
| ID: 11570 | Rating: 0 | rate:
| |
|
I just saw the new 32 bit version for ATI GPU. It's a good news, but is there any performance difference between 32 and 64 bits ? If the calculation times are the same, I will come back to my Xp 32 bits ^^ | |
| ID: 11584 | Rating: 0 | rate:
| |
|
Another question (sorry if it's stupid ^^) : why the optimized application, specially the GPU app, are not available on the MW website with a big-red-flashing font ? :) I found this thread only by (extreme) luck, and I think that a lot of people don't know they can optimize their participation. But maybe it will be a charge to heavy for the server ? | |
| ID: 11624 | Rating: 0 | rate:
| |
Another question (sorry if it's stupid ^^) : why the optimized application, specially the GPU app, are not available on the MW website with a big-red-flashing font ? :) I found this thread only by (extreme) luck, and I think that a lot of people don't know they can optimize their participation. But maybe it will be a charge to heavy for the server ? Because the developement is not finished yet. It runs, yes, but there are still some issues that should be resolved before it is ready for prime time. There are some reasons why the thread title is "GPU app teaser" and the applications are clearly labeled as an alpha test. The 32Bit variant exists 20 hours now and the very first feedback indicated there may be some problem with XP32 and the HD3800 series cards. It is not tested much (the 32bit compilation not at all, I have no possibility to do it). That's the reason a small scale test may be better in the beginning than to have to pull back a faulty application after a full blown rollout. | |
| ID: 11627 | Rating: 0 | rate:
| |
I just saw the new 32 bit version for ATI GPU. It's a good news, but is there any performance difference between 32 and 64 bits ? There shouldn't be any significant difference. | |
| ID: 11628 | Rating: 0 | rate:
| |
It's my personal opinion, but I think that a full list of compatible GPUs might be great, because I can read here and there some questions about the compatibility of cards. Maybe the label "HD38x0 or HD48x0" isn't clear for all people. Maybe something like this : Is this list updated.. I am doing a quick inventory on my hosts and to my surprise I have found several with ATI cards.. Not sure if they are compatible... ____________ . | |
| ID: 11647 | Rating: 0 | rate:
| |
I am doing a quick inventory on my hosts and to my surprise I have found several with ATI cards.. Not sure if they are compatible...
| |
| ID: 11648 | Rating: 0 | rate:
| |
|
Okay, so far, a speed report. | |
| ID: 11651 | Rating: 0 | rate:
| |
I am doing a quick inventory on my hosts and to my surprise I have found several with ATI cards.. Not sure if they are compatible... Will a 4550 work ? I have a couple of those. ____________ . | |
| ID: 11652 | Rating: 0 | rate:
| |
I am doing a quick inventory on my hosts and to my surprise I have found several with ATI cards.. Not sure if they are compatible... Unfortunately not, they don't have the required capabilities. :( The Task/CPU limit has been increased to 5000. | |
| ID: 11653 | Rating: 0 | rate:
| |
Okay, so far, a speed report. Is that one task every third of a minute? ____________ | |
| ID: 11654 | Rating: 0 | rate:
| |
Okay, so far, a speed report. I have 4 tasks running at once, which all finish in 60-62 seconds at the same time. 60/4=15 seconds each. 1/4th of a minute per task. | |
| ID: 11656 | Rating: 0 | rate:
| |
|
| |
| ID: 11657 | Rating: 0 | rate:
| |
I am doing a quick inventory on my hosts and to my surprise I have found several with ATI cards.. Not sure if they are compatible... Hummm.... They make an AGP version of the HD3850 if this works, this would be a cheap way to make older hardware scream for about $120 US. Would you forsee any problems running and AGP version of the HD3850? Here's a link to a card: http://www.newegg.com/Product/Product.aspx?Item=N82E16814102730 | |
| ID: 11658 | Rating: 0 | rate:
| |
1. Yes, CUDA is for Nvidia cards. 2. 9.1 is known to cause people some issues with performance not of crunching, but of the desktop while crunching. This may or may not have been fixed. 3. Not that I know of. 4. Yep.. Screenshot, I couldn't resist. I still can't believe what amazing work this is! Screenshot ____________ | |
| ID: 11660 | Rating: 0 | rate:
| |
Screenshot, I couldn't resist. I still can't believe what amazing work this is! 100% in 6 to 9 seconds. Amazing. I've been looking at the rumours about the ATI Raedon HD 4890 coming out in April with 960 stream processors and 48 texture units. Apparently there will be an overclocked version which will beat the HD 4870 with 25-30 percent performance boost with 1GB GDDR5 memory. I'm saving my pennies already ;) ____________ | |
| ID: 11679 | Rating: 0 | rate:
| |
Screenshot, I couldn't resist. I still can't believe what amazing work this is! Can I have your old one? I just have a Radeon 9600. ;P ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 11680 | Rating: 0 | rate:
| |
Screenshot, I couldn't resist. I still can't believe what amazing work this is! Sorry, but it's welded inside a laptop, and it's not that old, just a month or so - a Nvidia GeForce 9600M GT. I've just finished my 8th GPUGRID WU with it netting me a nice 2,479 credits. (While is been crunching CPDN and MW at the same time ;) ____________ | |
| ID: 11684 | Rating: 0 | rate:
| |
|
I think I have a little problem : | |
| ID: 11774 | Rating: 0 | rate:
| |
|
It works now, sorry for the previous message ^^ | |
| ID: 11777 | Rating: 0 | rate:
| |
I think I have a little problem : I upped the limit to 5000, its probably not enough :P Didn't want to jump all the way to 10k and have craziness start happening. ____________ | |
| ID: 11791 | Rating: 0 | rate:
| |
|
what is the latest version of the gpu app? I'm currently using 0.17 and not sure if their is an update i should be using. If there is any reason to upgrade or known problems? | |
| ID: 11792 | Rating: 0 | rate:
| |
I upped the limit to 5000, its probably not enough :P Didn't want to jump all the way to 10k and have craziness start happening. You don't need to raise it until the multiple GPU support is working. 10,000 WUs a day on a dual core are just enough for a HD4870 at stock speed. | |
| ID: 11793 | Rating: 0 | rate:
| |
what is the latest version of the gpu app? I'm currently using 0.17 and not sure if their is an update i should be using. If there is any reason to upgrade or known problems? The latest version would be 0.19 (the link is some posts above), but nothing changed besides a CPU detection like in the CPU version 0.19. A GPU detection would have made more sense ;) So I would regard an upgrade as optional and not needed atm. Well, 32Bit Win systems are supported now, too. Actually the 32Bit app still needs some testing, the known problems are quite similar to the 64Bit version I guess. But according to some reports, it may not be such a problem to run GPU-Z when the GPU is used as it is with the 64Bit version. But that's more of a speculation. If the ones running the app provide some feedback about their settings and the stability, it would be great. | |
| ID: 11794 | Rating: 0 | rate:
| |
|
I'm trying GPU app on a XP-32 bits. | |
| ID: 11799 | Rating: 0 | rate:
| |
|
Tried to remotely reboot and modified the boot.ini ... and it's crashed :( So I can't test anymore at this time :( | |
| ID: 11802 | Rating: 0 | rate:
| |
If the ones running the app provide some feedback about their settings and the stability, it would be great. So where's the best place to get one of these cards and drivers at the best price in the UK? I quite fancy having a go at this card crunching. [edit] Ahem, I would like to add that I would not buy such a card just for gaining credits, or heaven help me to just to help a scientific project, but I'm sure it would also improve the graphic capability for my digital photography hobby and general usablity of my PC system(s). And I'd be dying to see how it performs on the latest Red Alert game :p ____________ | |
| ID: 11804 | Rating: 0 | rate:
| |
|
A Few of Questions Please: | |
| ID: 11806 | Rating: 0 | rate:
| |
1: Boinc 6.4.5 does not "find" CUDA after upgrading.. I am assuming this is OK?1. Yes, CUDA is for Nvidia cards. Another ATI newbie here :) I've got my hands on a HD4870, installed boinc 6.4.5, catalyst 9.1 drivers and copied the 3 files from the Milkyway_0.19_ATI\Win32_SSE2 directory into projects\milyway... Boinc starts up, finds app_info.xml but every MW WU fails with Output file ps_s22_8_93171_1235143844_0_0 for task ps_s22_8_93171_1235143844_0 absent Any idea what I'm doing wrong? WinXP32 Pro BTW edit I have amdcalcl64.dll amdcaldd64.dll and amdcalrt64.dll in c:\windows\system32 | |
| ID: 11808 | Rating: 0 | rate:
| |
|
I was getting the same error. | |
| ID: 11817 | Rating: 0 | rate:
| |
I think I have a little problem : On SETI and GPU grid, after a certain number of errors in a row by the gpu tasks, they stop sending them for a day so as not to cause problems. I blew through about 36 last night really fast before I realized it wasn't working properly. Maybe that's something to add to the todo list as more people try gpu crunching. | |
| ID: 11821 | Rating: 0 | rate:
| |
1: Boinc 6.4.5 does not "find" CUDA after upgrading.. I am assuming this is OK?1. Yes, CUDA is for Nvidia cards. This is caused by an incorrect version or a corrupt version of Catalyst. I had the same issue a few posts above and reinstalled 8.12. ____________ | |
| ID: 11848 | Rating: 0 | rate:
| |
Thanks Beremat & Slicker for your adviceBoinc starts up, finds app_info.xml but every MW WU fails with I've downgraded to 8.12 but still get the same errors, have even de-installed & re-installed 8.12 to no avail I'll download it again and have another go :( | |
| ID: 11853 | Rating: 0 | rate:
| |
|
I'm getting alot of errors to. Got an Asus 3850 on Windows Vista 64 bit. I'm loading the latest Catalyst version right now. | |
| ID: 11854 | Rating: 0 | rate:
| |
|
Everyone getting errors should look in the task details and post the stderr output visible there. | |
| ID: 11860 | Rating: 0 | rate:
| |
Everyone getting errors should look in the task details and post the stderr output visible there. <core_client_version>6.4.5</core_client_version> <![CDATA[ <message> - exit code -1072365566 (0xc0150002) </message> ]]> hope that helps P4D, winxp32, HD4870, catalyst 8.12 | |
| ID: 11861 | Rating: 0 | rate:
| |
Everyone getting errors should look in the task details and post the stderr output visible there. That error normally means that some dll is missing. Most probably the app can't find the brook.dll distributed with the GPU app or one of the CAL libraries normally installed with the latest Catalyst drivers (8.12 or 9.1). Reinstalling the driver may solve the problem. | |
| ID: 11862 | Rating: 0 | rate:
| |
Boinc starts up, finds app_info.xml but every MW WU fails with Maybe BOINC just trashes the old WUs and new downloaded ones run fine? This could happen depending on the MW version you was running before changing to the GPU application. | |
| ID: 11863 | Rating: 0 | rate:
| |
This is caused by an incorrect version or a corrupt version of Catalyst. I had the same issue a few posts above and reinstalled 8.12. Your Core2Duo with WinXP32 SP3 is running really nice! In your task list one can see about 800 sucessfully crunched WUs without a single one that errored out. It shows the possibility to run the app flawlessly. Have you done anything special? Are you running another project at the same time? | |
| ID: 11864 | Rating: 0 | rate:
| |
|
One important note, I can only recommend not to update to the latest Catalyst 9.2 drivers. Obviously ATI accidentally renamed the CAL libraries required for the GPU application in the latest driver package. | |
| ID: 11866 | Rating: 0 | rate:
| |
Everyone getting errors should look in the task details and post the stderr output visible there. <core_client_version>6.4.5</core_client_version> <![CDATA[ <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000000001003B6BD write attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... | |
| ID: 11868 | Rating: 0 | rate:
| |
That error normally means that some dll is missing. brook.dll is in the projects/milkyway directory along with the app and app_info.xml and I have the 3 amdcal*.dll files in windows\system32 btw the cals are the 32bit versions not the 64bit versions I posted earlier, I copied & pasted from the previous message without noticing that refered to 64bit. I'll download 8.12 again Maybe BOINC just trashes the old WUs and new downloaded ones run fine? This could happen depending on the MW version you was running before changing to the GPU application afraid not, boinc is new to this machine today, specially for the HD4879, hostid 50557. Its set to NNW apart from when I retry after changing something ie reinstall drivers etc edit DOH, the machine is a P4 not a P4D | |
| ID: 11869 | Rating: 0 | rate:
| |
|
| |
| ID: 11876 | Rating: 0 | rate:
| |
Everyone getting errors should look in the task details and post the stderr output visible there. But most of the WUs on that computer run without error. Do you get VPU recover warnings (can be disabled if it's causing too much trouble) or do you start some application what is causing the errors? You could try to reduce the number of WUs running concurrently by changing the avg_ncpus and max_ncpus values in the app_info.xml (raise it to the number of cores in your system for only 1 WU at a time). | |
| ID: 11882 | Rating: 0 | rate:
| |
Question... Do you get errors if you try to fully load the GPU and the remaining cores with different projects or does the BOINC client simply refuse to run another project at the same time as MW? I thought I have seen some guys are running several projects along with the MW GPU app. Edit: Beremat provided a screenshot in this thread showing he is at least attached to several projects at once. Maybe he can answer if he was able to run them at the same time. I got a report that one gets a VPU recover error if other projects run with the MW GPU app creating a 100% CPU load. He said a possible workaround is to configure BOINC to use only 3 cores on a Quadcore. Obviously noone tried to simply deactivate the VPU recover feature yet. May be worth a shot. | |
| ID: 11885 | Rating: 0 | rate:
| |
This is caused by an incorrect version or a corrupt version of Catalyst. I had the same issue a few posts above and reinstalled 8.12. Thanks :3 I haven't done anything at all. I've run through at least 8-9,000 WUs so far. The only thing I suggest is to snooze/close BOINC while running *any* games, even 2D ones. Even rather low-quality graphic games like WoW will cause these WUs to error out. I was running a few projects before, and I was not getting any errors whatsoever. It seemed as though 2 other projects' WUs could run alongside. One would get 100% of one core, and the other would only get some percentage of the other core when MW wasn't using the CPU. Now, I'm running 100% MilkyWay. I'm getting around 45,000 credits over 24 hrs at a steady rate right now. Remember, this is only 1 4850! ____________ | |
| ID: 11894 | Rating: 0 | rate:
| |
Question... Nope no errors at all - only MW WU's crunch, until the cache of MW is empty, then the other project kicks in. I am currently running 8 MW WU's at a time - I only am seeing about 25-30% CPU load. ____________ . | |
| ID: 11896 | Rating: 0 | rate:
| |
2. I had to install Microsoft .NET Framework v2.0 for x64. It didn't like that I had .NET v3.5 installed which I thought was supposed to be an extension to 2.0. It wanted 2.0 as well. I didn't read this line properly. I already had .net framework 2 installed and thought that was all I needed. After numerous re-installs of the catalyst drivers & boinc I realised I should also install .net framework 3.5 After it rebooted all is working :) WOOHOO running 4 WUs at a time with each taking 13 seconds Stunning work Cluster Physik just to recap I needed both .NET Framework V2.0 and V3.5 | |
| ID: 11898 | Rating: 0 | rate:
| |
2. I had to install Microsoft .NET Framework v2.0 for x64. It didn't like that I had .NET v3.5 installed which I thought was supposed to be an extension to 2.0. It wanted 2.0 as well. Just installed a second card on an XP64 box w/ a Q9450. I ONLY installed .NET 2.0 SP1 and it worked fine. Maybe the issue is that the catalyst driver needs SP1? .NET 3.5 is NOT installed on the box. Hmmm.... Glad it worked for you though. | |
| ID: 11902 | Rating: 0 | rate:
| |
|
New install on a Q9450 running XP64 w/ Boinc 6.4.5. It runs 8 gpu WUs at a time. Nice. But, it will only download 12 WUs as if it only recognizes that it has 1 cpu rather than 4 cores. How can I get it to download 12 per core? Or, is it because it is only running on 1 cpu (no other projects) that it will only download 12 at a time? | |
| ID: 11903 | Rating: 0 | rate:
| |
what is the latest version of the gpu app? I'm currently using 0.17 and not sure if their is an update i should be using. If there is any reason to upgrade or known problems? Windows 32/64 ATI version 0.19 are now in zslip.com and zslip.net Thanks again Cluster Physik ____________ | |
| ID: 11906 | Rating: 0 | rate:
| |
|
Well, Frys had a 4870 on sale for $199 with discount and rebate... kinda hard to turn that down ... so ... | |
| ID: 11913 | Rating: 0 | rate:
| |
So, I guess what I am asking, has anyone been able to run MW GPU while running other projects? Beremat has answered this. He has a HD4850 paired with a C2D 8400 running WinXP32. I was running a few projects before, and I was not getting any errors whatsoever. It seemed as though 2 other projects' WUs could run alongside. One would get 100% of one core, and the other would only get some percentage of the other core when MW wasn't using the CPU. | |
| ID: 11920 | Rating: 0 | rate:
| |
|
I wonder what he did ... cause it does not work for me ... if I start up any other project, even FreeHal I lose one task on the ATI GPU ... so, for example I have FreeHAL enabled and only have 7 tasks running on the GPU ... if I suspend that task I get 8 on the GPU ... if I allow normal operation I get no GPU activity... | |
| ID: 11938 | Rating: 0 | rate:
| |
I wonder what he did ... cause it does not work for me ... if I start up any other project, even FreeHal I lose one task on the ATI GPU ... so, for example I have FreeHAL enabled and only have 7 tasks running on the GPU ... if I suspend that task I get 8 on the GPU ... if I allow normal operation I get no GPU activity... Not really. Running fewer tasks concurrently on the GPU does not lower the througput, it is perfectly okay. And remember that BOINC is not aware that the MW GPU app actually uses the GPU (no ATI support yet). It is scheduled like a normal CPU application. On newer versions (6.2 and up I think) it obeys the avg_ncpus and max_ncpus values in the app_info.xml. They are set to 0.5 and 1 respectively, to allow for an easier overlap of at least two WUs (increases efficiency and GPU load slightly, but more than two do not help) also with a lower resource share. But one can also play around with the values. But this actually just influences how many tasks BOINC schedules to run, not how much of a core is really used. You can save some CPU time on the GPU application (effectively freeing up a bit of the one full core the GPU app takes irrespective of the number of concurrently running MW WUs) if you lower the values and reduce the MW resource share accordingly. Just an example, you have a quad core, the MW resource share is at 25% and some other project is at 75%. BOINC will then run two MW WUs concurrently (using one core) and three additional WUs from that other project with the default settings in the app_info.xml. That's perfectly okay, as the throughput of the GPU app does not depend on the number of concurrent WUs (as longs as two or more are running, but even that is only a 10% effect, even less on the slower HD3800 series). After all, you have only one GPU. It's almost like running multithreaded on a single core. That scenario will give you 100% CPU load and still the maximal throughput of the MW GPU application. Now reduce the avg_ncpus values in the app_info to 0.25 (the max_ncpus should stay at 1). With the same resource share settings as above (25/75) there will still be 3 WUs from the other project, but now 4 MW units. That should still give the same troughput as with the 2 WUs from above. But now you could also reduce the MW share a bit to let's say 13/87. The BOINC scheduler will run in most cases 4 WUs of the other project and only 2 MW WUs. Effectively 5 active tasks (as I explained basically all MW tasks together counts as only one in this respect no matter how many WUs actually run) battle for the 4 cores of the system. The throughput of the other project should rise slightly with his approach and MW should not take too much of a hit (has to be tested though). Hope this may shine some light on the issue. | |
| ID: 11949 | Rating: 0 | rate:
| |
|
Should I change the avg_ncpus from the default value when using a dual-GPU card (4870x2)? | |
| ID: 11961 | Rating: 0 | rate:
| |
|
Some light, though I think I am drowning ... still ... | |
| ID: 11964 | Rating: 0 | rate:
| |
Should I change the avg_ncpus from the default value when using a dual-GPU card (4870x2)? In the moment multiple GPUs are not supported (but hopefully I will find some time to put it in). In principle the app should use just one of the GPUs on your card. With multiple cards in a system it is the same. But could you please test that it runs at all? Editing of the app_info.xml is not needed if all is running well. By the way, a single HD4870 is already that fast. Do you imagine what two of them would do? :o | |
| ID: 11965 | Rating: 0 | rate:
| |
Some light, though I think I am drowning ... still ... So let's make it simple. A HD4870 finishes about 400 WUs (of the short type) per hour. It does so if you run 2 WUs at a time, and it still arrive at the same throughput as if you would run 4, 8 or even 16 WUs concurrently on that single card. The throughput does not rise like on a a multi core CPU (there is only one GPU). So just fire up some other projects. As longs as there is at least one running MW task left, you will generate one result every 9 seconds (wall clock time). And with less concurrent MW tasks you get an even better impression of the speed ;) | |
| ID: 11966 | Rating: 0 | rate:
| |
I upped the limit to 5000, its probably not enough :P Didn't want to jump all the way to 10k and have craziness start happening. and with the longer wu's 5k is probably enough. though I noticed on the i7: Maximum daily WU quota per CPU 4999/day and it was only 4998/day when I looked earlier while all the other machines showed 5000. and since we've gotten longer work units, i've been having problems with the GPU app freezing after about 4 hours - i7 with ati 4800. so, this morning, I updated to CCC 9.1. Then noticed it froze after 2 1/2 - 3 hours when i checked it from my phone. when I got home tonight, it didn't look like 9.1 installed correctly. So I completely uninstalled and reinstalled 9.1, then it would freeze up after an hour or so. I just installed the new .19 gpu app, so maybe that will clear it up? but i wonder if b/c these are longer wu's, that I'm just putting too much strain on the gpu continuously crunching 16 wu @ a time? | |
| ID: 11979 | Rating: 0 | rate:
| |
But could you please test that it runs at all? Oh yes, the app works just as intended, I guess, chewing through one WU every 8-12 seconds (depending on the WU). By the way, a single HD4870 is already that fast. Do you imagine what two of them would do? :o Having two GPUs available, and knowing that one of them will remain idle for now, imagining is just about all I do. But hey, at some 50 times the speed of one 4.0 GHz Yorkfield core (stock app), I'm already laughing :D | |
| ID: 11982 | Rating: 0 | rate:
| |
[quote]I upped the limit to 5000, its probably not enough :P Didn't want to jump all the way to 10k and have craziness start happening. Hm, I doubt that you're overstressing your card. It is likely that there is a fault with the drivers somewhere. I've been crunching for around 46 hours straight on my 4850 with Catalyst 8.9, and no errors apart from when I was gaming. I suggest you rollback to 8.9 and see how it goes. EDIT: Oh! Another thing. Monitor your temperatures on your GPU while crunching if you can. I had to increase the fan speed on my 4850 to 50% because I was afraid that 85C was a bit much. Even this slight increase from 30 to 50% cooled the card all the way down to 63C stable. Also, note that I haven't done a single WU on MilkyWay with my CPU ever. All the results you see on the left are with one single GPU in 46 hours, just under 2 days. Subtract around 8 hours because I was gaming. That makes around 38 hours. 100,000 credits\38 hours=2.6k credits/hr on a 4850, imagine what a 4870 can do! ____________ | |
| ID: 12015 | Rating: 0 | rate:
| |
So let's make it simple. I guess I was seduced by the image of 8 tasks running at the same time ... With two GTX 295s in one of my other systems it is easy to get seduced by the thrill of speed ... I guess that I was also getting suckered by the fact that I did not have the debts right so the MW tasks were not running. But, now the system seems to be content and is running the tasks through quite nicely ... though I only have one in flight at a time ... so I will see how it goes ... Thanks for the help ... what the heck ... it seems to be running ... now I have to look at my other systems to make sure they are still cooking along too ... Thanks again ... | |
| ID: 12037 | Rating: 0 | rate:
| |
|
Upgraded to GPU app version 0.19. | |
| ID: 12043 | Rating: 0 | rate:
| |
i left it at 9.1 but took your advice of upping the fan speed. that's brought it down from ~83c to ~77c. and it made it through the night without locking up. So it could be that it was overheating. But I had also upgraded to version .19. So, was there a change in there that corrected the problem? either way, v.19 is working fine on an i7 and hd4870 with 512m | |
| ID: 12065 | Rating: 0 | rate:
| |
i left it at 9.1 but took your advice of upping the fan speed. that's brought it down from ~83c to ~77c. Besides the CPU detection nothing changed between 0.17 and 0.19. So maybe really a temperature problem. But I have seen your crunch times are slightly on the high side. This could be caused by running too many WUs concurrently on the GPU. At a certain point the RAM on the graphics card is not sufficient for the number of WUs taking space there. Before it errors out (when even more WUs would be crunched), it slows down (probably some swapping over PCI-Express happens). And with 16 WUs it is getting already a bit crowded on a 512MB card. Another reason for the higher times could be that the card runs downclocked in a power saving mode. Maybe you should check the clock speed of the card. Furthermore you may think about attaching to a second BOINC project with that i7. This will reduce the number of MW WUs that are running a he same time, but not the throughput. You will still finish the same number of WUs per hour even with less concurrently running WUs. In fact, it could even rise in your case. Furthermore your CPU cores wouldn't be idling that much ;) | |
| ID: 12067 | Rating: 0 | rate:
| |
|
Same message, again : not reporting or requesting tasks... I can't crunch today :( | |
| ID: 12073 | Rating: 0 | rate:
| |
i left it at 9.1 but took your advice of upping the fan speed. that's brought it down from ~83c to ~77c. off the top of my head, i remembered reading that you basically just changed the version number - but couldn't remember if that was just the opti app or the gpu. also, i've noticed the temp has dropped even further overnight, so I may reset the fan speed to 40%. and i have a climate prediction model sitting @ 50% done, so I'll resume that one. | |
| ID: 12106 | Rating: 0 | rate:
| |
|
I've noticed that if I enable both MW and another project, that it will run both but that the MW gpu app will SHARE a cpu with the other project. e.g. Q9450 runs 4 ABC apps and 1 or 2 MW. 3 of the ABC run on their own cpu. The 4th ABC runs on the same cpu as the MW app(s). When the CUDA apps do this, they set their priority to "Below Normal" instead of "Low" (a.k.a. Idle). Any chance the gpu app could be modified to do the same? Then, whatever processing power is left will go to the other app since it will be set to Low. | |
| ID: 12128 | Rating: 0 | rate:
| |
But could you please test that it runs at all? I forgot to mention that the CPU usage so far hasn't exceeded 23% of one core (still 4.0 GHz Yorkfield). Much less most of the time. Kudos to everyone involved! ____________ | |
| ID: 12131 | Rating: 0 | rate:
| |
I've noticed that if I enable both MW and another project, that it will run both but that the MW gpu app will SHARE a cpu with the other project. e.g. Q9450 runs 4 ABC apps and 1 or 2 MW. 3 of the ABC run on their own cpu. The 4th ABC runs on the same cpu as the MW app(s). When the CUDA apps do this, they set their priority to "Below Normal" instead of "Low" (a.k.a. Idle). Any chance the gpu app could be modified to do the same? Then, whatever processing power is left will go to the other app since it will be set to Low. That scheduling problem is hard to solve as long there is no ATI support in BOINC. Maybe it will come with 6.7. But as the GPU app uses quite little CPU resources (the core used in the moment is mainly for polling the GPU, less than 2 seconds CPU time for a WU are really needed), there is the chance I can free up some of it. That would reduce the problem I guess. | |
| ID: 12158 | Rating: 0 | rate:
| |
|
Ha ha, I love it. Claimed credit 0.01 Granted credit 8.44 | |
| ID: 12159 | Rating: 0 | rate:
| |
Kudos to everyone involved! Basically, that's just me ;) But I guess you also have to thank the two guys from my team Planet3DNow! who didn't hesitate to test the very first incarnations of the app, when it did crash on virtually every WU and didn't delivered any results let alone credits. Thank you HiRN and L@MiR/Emploi! You have to know I do the GPU coding in some kind of a vacuum. I don't have a compatible card yet to test it for myself. That will be some kind of a problem for the multi GPU stuff. We will see how this works out. | |
| ID: 12162 | Rating: 0 | rate:
| |
Kudos to everyone involved! L@Mir? Fantistic! (Hello again :) and HiRN also - many thanks! :) ____________ | |
| ID: 12166 | Rating: 0 | rate:
| |
7 to 12 seconds a WU. Amazing! Sorry, but it isn't that fast ;) The CPU time gives a good indication for the throughput in the moment, in your case it means a WU finishes every 7 to 12 seconds, but not every 3. Take a stopwatch if you don't believe it ;) | |
| ID: 12167 | Rating: 0 | rate:
| |
7 to 12 seconds a WU. Amazing! Ah, I see, they took less than a minute so somewhere more around 25 seconds - without doing a precise test (I wish I had a stop watch....) [edit] 4 ran in 64 seconds - that's 16 secs a WU. Is that about right? ____________ | |
| ID: 12168 | Rating: 0 | rate:
| |
Ah, I see, they took less than a minute so somewhere more around 25 seconds - without doing a precise test (I wish I had a stop watch....) For the longer dual stream WUs (12 to 13 credits) it is the right time for a HD4850 (a 4870 would be 20% faster). The shorter single stream WUs (~8 credits) should take 10 to 11 seconds or so on your card. | |
| ID: 12184 | Rating: 0 | rate:
| |
|
BoincView looked like a scene from "The Shining" after I installed Catalyst 9.2, and I also noticed 0% load on the GPU. Reverted to 9.1, and the WUs again finished without errors. Has anyone else tried the latest incarnation of the driver? | |
| ID: 12186 | Rating: 0 | rate:
| |
Ah, I see, they took less than a minute so somewhere more around 25 seconds - without doing a precise test (I wish I had a stop watch....) Aha, you've worked out which card I have ;) ____________ | |
| ID: 12191 | Rating: 0 | rate:
| |
BoincView looked like a scene from "The Shining" after I installed Catalyst 9.2, and I also noticed 0% load on the GPU. Reverted to 9.1, and the WUs again finished without errors. Has anyone else tried the latest incarnation of the driver? I got the HD4850 today which came with the 8.5 catalyst driver. That didn't work. I then tried a 9.1 which wouldn't work at all, but I think it was for Vista (I have XP). I tried the 9.1 for XP and it worked, but it seemed like the 4 WUs were going to take forever. So finally I located the 8.12 driver for XP and it works a treat. ____________ | |
| ID: 12194 | Rating: 0 | rate:
| |
BoincView looked like a scene from "The Shining" after I installed Catalyst 9.2, and I also noticed 0% load on the GPU. Reverted to 9.1, and the WUs again finished without errors. Has anyone else tried the latest incarnation of the driver? Just look here. If you really want to use the Cat 9.2 driver, it should be possible to manually rename the three atical*.dll files in the Windows/system32 folder to amdcal*.dll. Someone in my team tried and it worked. @Ice: Could you add a note to zslip, that the Cat 9.2 is not working with the GPU application? And the older 0.17 GPU app is only available for Win64, not Win32/64 as stated there. | |
| ID: 12205 | Rating: 0 | rate:
| |
BoincView looked like a scene from "The Shining" after I installed Catalyst 9.2, and I also noticed 0% load on the GPU. Reverted to 9.1, and the WUs again finished without errors. Has anyone else tried the latest incarnation of the driver? Sure, I'll do that [edit] done ____________ | |
| ID: 12208 | Rating: 0 | rate:
| |
But as the GPU app uses quite little CPU resources (the core used in the moment is mainly for polling the GPU, less than 2 seconds CPU time for a WU are really needed), there is the chance I can free up some of it. That would reduce the problem I guess. The "ideal" is to use the IRQ so that there is zero load on the CPU unless it is needed. Though they have not shared technical details with the community it looks like that is what GPU Grid did... last month they were using idle polling and were consuming up to a whole core per GPU core. Then they made a change and the CPU time dropped to less than 1% ... Small hit to speed where the application takes about 8-10% longer to run over 4-20 hours ... with 9-14 second run times I am not sure that I would even notice the change ... but, would have less load on the CPUs ... If they are using the standard windows API to get the GPU id adding the ATI cards should be a no brainer, all it is is a different look-up table ... As I said in the other thread I sent them the notes on that but no reply so I don't know if they even looked at it or not ... in that I can't write C code no point in me trying ... but it does not look that hard to modify the BOINC software to pick up an ATI card ... | |
| ID: 12231 | Rating: 0 | rate:
| |
The "ideal" is to use the IRQ so that there is zero load on the CPU unless it is needed. Though they have not shared technical details with the community it looks like that is what GPU Grid did... last month they were using idle polling and were consuming up to a whole core per GPU core. Then they made a change and the CPU time dropped to less than 1% ... I thought about a bit different and higher level solution to it. But it should be also quite effective. 1% CPU load is not possible with the current split of the work between GPU and CPU. I don't plan to change anything on that because the effort for doing the remaining 0.1% of the CPU calculations on the GPU appears to be too much. If all the more urgent issues are solved, maybe one can think about it again. But I doubt the conclusion will be much different. One needs the CPU about half a second in the beginning and slightly more (about a second) at the end of a WU (scales with CPU speed of course). In between a CPU load of about 10% of a core or maybe even less should be doable. | |
| ID: 12242 | Rating: 0 | rate:
| |
The "ideal" is to use the IRQ so that there is zero load on the CPU unless it is needed. Though they have not shared technical details with the community it looks like that is what GPU Grid did... last month they were using idle polling and were consuming up to a whole core per GPU core. Then they made a change and the CPU time dropped to less than 1% ... Then perhaps the next challenge is to make the ATI GPU recognized and managed by BOINC? | |
| ID: 12298 | Rating: 0 | rate:
| |
Then perhaps the next challenge is to make the ATI GPU recognized and managed by BOINC? I've heard somewhere it will be in 6.7. | |
| ID: 12301 | Rating: 0 | rate:
| |
|
I would like to know how much more productive it is expected to be a HD4870 versus a HD4850. | |
| ID: 12360 | Rating: 0 | rate:
| |
I would like to know how much more productive it is expected to be a HD4870 versus a HD4850. 20% As the number of shaders is identical for both cards, the difference comes just from the clock speed, 750 vs 625 MHz. 750/625 = 1.2 The higher memory bandwidth of the HD4870 is of no use for MW. It is not a limiting factor, that's the shader throughput. | |
| ID: 12367 | Rating: 0 | rate:
| |
I would like to know how much more productive it is expected to be a HD4870 versus a HD4850. I take it the power of the host computer makes no difference, or does, for example, CPU or RAM in the computer make a difference to the card's performance? ____________ | |
| ID: 12373 | Rating: 0 | rate:
| |
I would like to know how much more productive it is expected to be a HD4870 versus a HD4850. Such a difference should be almost nonexistent as long as at least 2 WUs run concurrently. That enables the possibility to hide the CPU part of one WU during the GPU computations of another one. | |
| ID: 12424 | Rating: 0 | rate:
| |
|
the gpu app has been running a little funny today Normally it only runs one at a time this morning it was running 4-5 at a time and bogging down the system quite a bit. I rebooted and that seemed to fix it, for a little while but now it's not running at all, and has a message on a wu saying waiting to run (.50 cpus). Is it waiting for my other projects to finish up on the cpu for some reason even though it can run while they are still going? | |
| ID: 12449 | Rating: 0 | rate:
| |
the gpu app has been running a little funny today Normally it only runs one at a time this morning it was running 4-5 at a time and bogging down the system quite a bit. I rebooted and that seemed to fix it, for a little while but now it's not running at all, and has a message on a wu saying waiting to run (.50 cpus). Is it waiting for my other projects to finish up on the cpu for some reason even though it can run while they are still going? These scheduling problems are caused by the fact that the BOINC Client does not know the app is running on the GPU. It is scheduled like a normal app running on the CPU. | |
| ID: 12473 | Rating: 0 | rate:
| |
i left it at 9.1 but took your advice of upping the fan speed. that's brought it down from ~83c to ~77c. I enabled CPDN and ABC but MW always ran 16 apps, then would switch to 8 ABC, never sharing - it was like how the Cylons and Humans can't get along, it always had to be one or the other never both. But with 16 MW's running it would eventually lock up. It really does look like a ram problem, the 512 really can't handle a constant run of 16 Apps of this length. Though I didn't have trouble earlier with the shorter apps. So, what I finally did was reset boinc to only run with 6 CPU's max. Now with only 12 wu's running at a time, the GPU seems much happier and doesn't lock up. And the actual crunch times are significantly shorter with only the 12. 2 - 3 mintues compared to the 8 or 9 when running 16. And as you pointed out, I end up processing more wu's. | |
| ID: 12476 | Rating: 0 | rate:
| |
- it was like how the Cylons and Humans can't get along, it always had to be one or the other never both. I've been running the HD4850 on version 0.19 for just over 24 hours now and the phrase 'running like the clappers' comes to mind ;) I've tried to share with CPDN, but it instantly drops from a rapid 4 x 0.5 CPU to a very slow 2 x 0.5 CPU. To be honest I can run CPDN on another box and the 4 x 0.5 clappers is more than enough throughput for me on this one box. However, if a way to share with the Cylons can be found, it would be nice ... ____________ | |
| ID: 12492 | Rating: 0 | rate:
| |
|
All right, got the GPU app working, under Windows 7 no less. Two problems: BOINC was using a protected install, and the DLLs for stream were missing. First was easy to correct with a reinstall, and the DLLs I tried grabbing from Vista x64, worked like a charm. So in exchange for some graphics performance, I get 4 ABC and 4 MW WUs running all at the same time. Great app Cluster Physik. ;) | |
| ID: 12575 | Rating: 0 | rate:
| |
|
Please, I need to know if the Win32/ATI/0.19 application will work under Vista 32 bits O.S. I have a just-bought hd4850 and I need to know it before I open the box breaking the seals | |
| ID: 12606 | Rating: 0 | rate:
| |
|
I have BOINC 6.4.5 installed as a protected service on XP64 (domain member), and it works a charm with Catalyst 8.12 (even 9.1) and the GPU app 0.19 (all hail Cluster Physik!). <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> Running Milkyway@home ATI GPU application version 0.19 by Gipsel CPU: Intel(R) Xeon(R) CPU X3360 @ 2.83GHz (4 cores/threads) 4.00399 GHz (332ms) No compatible GPU found! </stderr_txt> After i killed Boing Manager and rebooted, things went back to normal again. Repeating the excercise led to an identical outcome. No biggie, bit it did get my attention. ____________ | |
| ID: 12637 | Rating: 0 | rate:
| |
All right, got the GPU app working, under Windows 7 no less. Two problems: BOINC was using a protected install, and the DLLs for stream were missing. First was easy to correct with a reinstall, and the DLLs I tried grabbing from Vista x64, worked like a charm. So in exchange for some graphics performance, I get 4 ABC and 4 MW WUs running all at the same time. Great app Cluster Physik. ;) Having discovered a stopwatch on my mobile phone I ran some tests and find that I can indeed run another project together with MW. I quite agree - Great app Cluster Physik. ;) ____________ | |
| ID: 12663 | Rating: 0 | rate:
| |
|
I previously tried Catalyst 9.1 for my HD4850 which crashed and left the MW tasks going snail-pace. | |
| ID: 12674 | Rating: 0 | rate:
| |
|
It worked great on Vista64, but on Xp32 I get always the same message : not requesting tasks ... the only solution I found was to suspend or delete the other projet (World Comm Grid). | |
| ID: 12693 | Rating: 0 | rate:
| |
|
Strange error message, also had 8 MW tasks with this error: | |
| ID: 12732 | Rating: 0 | rate:
| |
Not sure what it means, if it means anything, luck of the draw, bad day at black rock ... Bad day at black rock. If you're running the ATI then these tasks are over in a blink of an eye. Let them go. We cherish each one, I know. But there are many others to greet and to race by - in the blink of an eye... ;) ____________ | |
| ID: 12739 | Rating: 0 | rate:
| |
Not sure what it means, if it means anything, luck of the draw, bad day at black rock ... Hmm, well, I don't know about that ... I blink slowly, but not THAT slowly ... :) But you are right, I am too anal about losing the science ... | |
| ID: 12754 | Rating: 0 | rate:
| |
Not sure what it means, if it means anything, luck of the draw, bad day at black rock ... I know what you mean. I find it hard to micro manage so many machines, and especially have that 'Doh!' feeling when I find I've crunched the same CPDN WU and it ain't gonna give me no more credit the second time. I have to ditch some part run WUs 'just in case' I already finished them off somewhere else. Oh the joy of short MW tasks :) ____________ | |
| ID: 12759 | Rating: 0 | rate:
| |
|
Well, I don't have that many systems any more ... the wife has been on me to cut back and I have been doing so ... | |
| ID: 12774 | Rating: 0 | rate:
| |
But could you please test that it runs at all? Here's an update on the double-GPU HD4870X2 vs the single-GPU HD4870/1GB. HD4870/1GB runs at its highest configured clock speeds when under load from the MW app. Partly OC'ed to 800/900 MHz (gpu/mem) this means 5-8 seconds per WU. HD4870X2 runds at its idle clocks (500 MHz gpu) even with one GPU under load from MW, which means 8-12 seconds per WU. It seems that giving half the card something to do isn't enough to "wake it up" from idle/2D clocks. But yes, the GPU apps do work on this card as well, albeit somewhat slower than on its lesser sibling. ____________ | |
| ID: 12800 | Rating: 0 | rate:
| |
|
I have a team mate that is having trouble. | |
| ID: 12855 | Rating: 0 | rate:
| |
I have a team mate that is having trouble. Protected mode installation of BOINC is not going to work with GPU apps under Vista (same as CUDA). Or are you accessing the machine over a remote desktop connection? | |
| ID: 12856 | Rating: 0 | rate:
| |
I have a team mate that is having trouble. We did install BOINC in protected mode - Let me give him a call and see if that fixes it. ____________ . | |
| ID: 12858 | Rating: 0 | rate:
| |
|
@Cluster Physik | |
| ID: 12902 | Rating: 0 | rate:
| |
@Cluster Physik I think that's a good comment and I can sort that out on zslip. ____________ | |
| ID: 12912 | Rating: 0 | rate:
| |
@Cluster Physik Cool, I usually D/L and hang onto the versions till it is very clear that the new is the keeper. Just incase I have to back-level the application ... I do the same thing with BOINC Manager (in case they start to hide the old list, even paranoids have enemies) ... :) | |
| ID: 12915 | Rating: 0 | rate:
| |
@Cluster Physik I thought the same and 0.19c and 0.19d (and future versions) identify themselves as such. And before someone is looking in the P3DNow! forum and is trying one of the newer versions, I can't recommend that. The multi GPU scheduler is not working correctly in the moment and trashes most WUs. So one should stay with 0.19b for the time being. 4. Have you sent the detection code to UCB? We are at least two versions from when I sent them notes on OpenCL and "Brook" (and generic GPU identification using windows API), but it looks like someone has to do the dirty work ... and you already have ... (PM sent also about this) No, I didn't send it. But I've heard they got already some detection code. If all goes well it will be integrated in version 6.7 in the next month. | |
| ID: 12921 | Rating: 0 | rate:
| |
@Cluster Physik OK, zslip is updated so that the filenames also include OS, whether ATI, 32 or 64 bit, and version number. ____________ | |
| ID: 12922 | Rating: 0 | rate:
| |
No, I didn't send it. But I've heard they got already some detection code. If all goes well it will be integrated in version 6.7 in the next month. Maybe yours is better ... :) It could not hurt ... | |
| ID: 12932 | Rating: 0 | rate:
| |
1% CPU load is not possible with the current split of the work between GPU and CPU. I don't plan to change anything on that because the effort for doing the remaining 0.1% of the CPU calculations on the GPU appears to be too much. If all the more urgent issues are solved, maybe one can think about it again. But I doubt the conclusion will be much different. Does it makes sense to compile ATI GPU version with CPU SSSE3, SSE4.1 and/or SSE4.2 instructions? Or at least try to see how it would behave... ____________ BOINC Project specifications and hardware requirements | |
| ID: 12933 | Rating: 0 | rate:
| |
Does it makes sense to compile ATI GPU version with CPU SSSE3, SSE4.1 and/or SSE4.2 instructions? Or at least try to see how it would behave... No sorry, the ATI would never fit into my Core 2 SFF, there is not enough room inside and I couldn't get the lid back on, no way ;) ____________ | |
| ID: 12936 | Rating: 0 | rate:
| |
1% CPU load is not possible with the current split of the work between GPU and CPU. I don't plan to change anything on that because the effort for doing the remaining 0.1% of the CPU calculations on the GPU appears to be too much. If all the more urgent issues are solved, maybe one can think about it again. But I doubt the conclusion will be much different. The really needed CPU time per WU is about one second or so. The remaining one is just for polling the GPU, which is not going to be faster with SSEx. As the speed increases with anything above SSE2 (used by the GPU app) are minor ones, one could maybe shave off a tenth of a second. Hardly worth it. | |
| ID: 13441 | Rating: 0 | rate:
| |
But could you please test that it runs at all? Brickhead, what your saying is that your only running on one side of the x2 Video Card, but how many WU's are you running @ once with it by it's self or running another Project with it ??? | |
| ID: 13560 | Rating: 0 | rate:
| |
|
Oh shock horror, hooray :D I've got Catalyst 9.2 working. | |
| ID: 13571 | Rating: 0 | rate:
| |
Oh shock horror, hooray :D I've got Catalyst 9.2 working. A bit of a strange pattern of crunching at first and then when I tried to run a CPDN WU the 4 MW just froze. I then suspended one of them and the other 3 set off working. Now it's settled down to a pattern of 2 MW WU's crunching every 40ish seconds and a CPDN WU crunching away every 436 hours. I think that's slower that using using version 9.1 (not referring to CPDN), but then I'm not sure how long these new WUs take now. ____________ | |
| ID: 13577 | Rating: 0 | rate:
| |
Oh shock horror, hooray :D I've got Catalyst 9.2 working. I took it back to 9.1 and the 8.12 and with both it seemed slower than 9.2. I think it's these longer work units which I haven't baselined for myself yet. I've taken it back to 9.2 and it's been running overnight just fine with what seems to be good performance. It just seemed to take a little while to settle downn - a CPDN WU is crunching alongside 3 MW WUs nicely, all running with BOINC 6.4.6 (XP pro). ____________ | |
| ID: 13608 | Rating: 0 | rate:
| |
|
Maybe i found a bug in gpu application 19d. | |
| ID: 13620 | Rating: 0 | rate:
| |
Maybe i found a bug in gpu application 19d. I see. Basically that is a problem with some interference of the BOINC scheduler and the one build into the GPU app. If the WU, which owns the GPU in the moment gets evicted by the BOINC scheduler, the other WUs still "think" it is running, using the GPU and do not start. This behaviour should go away, if you disable the "leave aplications in memory" option. That way, the paused WUs are really stopped and not just suspended. But maybe easier, just don't fiddle around with suspending projects ;) PS: I still don't get why people raise the number of concurrent WUs. Two are really enough for maximum efficiency. So even taking the start/finishing of WUs into account, you will never need more than 3 WUs (default value) for maximum efficiency of the GPU. It would be better for the throughput, if you lower the wait factor closer to 1. Or are you just trying to avoid the eviction of WUs by the boinc manager? | |
| ID: 13653 | Rating: 0 | rate:
| |
|
w1.1 use to down gpu usage and sluggish behaviour of the user interface This is my home computer, and some time i am watching movie and doing something like that. | |
| ID: 13662 | Rating: 0 | rate:
| |
I still don't get why people raise the number of concurrent WUs. Two are really enough for maximum efficiency. So even taking the start/finishing of WUs into account, you will never need more than 3 WUs (default value) for maximum efficiency of the GPU. It would be better for the throughput, if you lower the wait factor closer to 1. Or are you just trying to avoid the eviction of WUs by the boinc manager? I agree, more in this case isn't neccessaraly better I have found right from the git go ... I'm running 3&3 3 MWay's & 3 Regular Wu's and getting 85,000-90,000 Per Day from 1 Card (4870 512mb with no Overclocking) ... | |
| ID: 13664 | Rating: 0 | rate:
| |
I'm running 3&3 3 MWay's & 3 Regular Wu's and getting 85,000-90,000 Per Day from 1 Card (4870 512mb with no Overclocking) ... That's crazy. :P It puts my 1 pc to shame. In 2 days you can put out more than my overall total, I did ~50k all of last year. I need a Gpu...(sigh). ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 13667 | Rating: 0 | rate:
| |
I don't understand the settings in the BOINC parameters, something to get into at some time, but I may have a tip that may work for others. I'm trying to get MW to run with another task, eg, CPDN, but usually 4 MW are running on their own. Not efficient as you pointed out Cluster Physik. So what I do is put MW on suspend, two CPDN tasks run (I'm hyper-threading). Then I resume the CPDN project. 4 MW tasks then 'freeze'. I then suspend one of the CPDN tasks and have two MW and one CPDN crunching away nicely. When things don't look right, exit the BOINC manager and restart it - that usually sorts it out for me. ____________ | |
| ID: 13686 | Rating: 0 | rate:
| |
I'm running 3&3 3 MWay's & 3 Regular Wu's and getting 85,000-90,000 Per Day from 1 Card (4870 512mb with no Overclocking) ... It's still about contributing what you can/want. Even with GPU, both ATI and nVidia, I'm still crunching the old fashioned way with actual computers and laptop ;P ____________ | |
| ID: 13687 | Rating: 0 | rate:
| |
This behaviour should go away, if you disable the "leave aplications in memory" option. That way, the paused WUs are really stopped and not just suspended. I set this option to disable, update project and try to suspend. Then i suspend abc, application remove from memory. But if suspend MW, all aplication leave in memory and not remove. | |
| ID: 13708 | Rating: 0 | rate:
| |
Brickhead, what your saying is that your only running on one side of the x2 Video Card, but how many WU's are you running @ once with it by it's self or running another Project with it ??? Doesn't matter. I've tried anything up to four WUs at once. GPU0 gets all the load it needs, and GPU1 remains idle. No surprise, given that multi-GPU functionality isn't built into 0.19 or 0.19b. I am however testing a new development version which supports multiple GPUs. Not quite the doctor's order, as the combined load still doesn't exceed what would fit in one GPU. So no practical improvement for X2 cards or crossfire yet AFAIK, but still an important step forward. I'm confident that our mastermind Cluster Physik will eventually be victorious in the battle against cold GPUs :) I do run four other projects in addition to MW on this quad-core dual-GPU machine, and by assigning resources 400 (MW) : 4 x 100 (others), I've managed to get 4 MW WUs running alongside 4 from the other projects. I had to set avg_ncpus very low (value * number_of_GPU_WUs_at_once < 1) to tell the BOINC CC that there is no need to kick any of the 4 "foreign" WUs to accomodate 4 MW WUs at the same time, in order to have all eight *running* simultaneously. ____________ | |
| ID: 13713 | Rating: 0 | rate:
| |
|
Okay, was just curious, so far I've just stuck with the single core cards but when dual core is enabled I may get one ... Thanks | |
| ID: 13723 | Rating: 0 | rate:
| |
|
I tried to get ATI Card to run the Milkyway WU's on the Linux side of a Dual Boot Windows/Linux Box but so far no luck. I installed the Linux 8.12 Drivers or at least I thought I did because everything seemed to go alright & the ATI Counsel showed up. I did it from the Terminal because when I tried to install them from a Counsel I got a error message saying something about a wrong ID. | |
| ID: 13816 | Rating: 0 | rate:
| |
I tried to get ATI Card to run the Milkyway WU's on the Linux side of a Dual Boot Windows/Linux Box but so far no luck. I installed the Linux 8.12 Drivers or at least I thought I did because everything seemed to go alright & the ATI Counsel showed up. I did it from the Terminal because when I tried to install them from a Counsel I got a error message saying something about a wrong ID. If you take a look at zslip you will see that the ATI cards and the optimization files made available for MilkyWay are only available to Windows 32 and 64 bit. No mention of it working for Linux, and none that I have heard about. ____________ | |
| ID: 13845 | Rating: 0 | rate:
| |
|
I could have sworn I seen a post by somebody saying they got some app to work in Linux but could be mistaken, anywho I didn't pay attention when I downloaded the Linux App, just thought it was for running the ATI Cards ... :) | |
| ID: 13851 | Rating: 0 | rate:
| |
I could have sworn I seen a post by somebody saying they got some app to work in Linux but could be mistaken, anywho I didn't pay attention when I downloaded the Linux App, just thought it was for running the ATI Cards ... :) There are certainly optimized apps for Linux by speedimic, but I don't think he's gotten round to ATI GPU, but I don't have Linux myself and I really don't know. ____________ | |
| ID: 13861 | Rating: 0 | rate:
| |
I could have sworn I seen a post by somebody saying they got some app to work in Linux but could be mistaken, anywho I didn't pay attention when I downloaded the Linux App, just thought it was for running the ATI Cards ... :) LOL, haven't even gotten round getting me a ati/nvidia card... only low-budget-onboard stuff here. ____________ mic. | |
| ID: 13967 | Rating: 0 | rate:
| |
The development of apps for GPU is really quite recent. If I recall, it is less than 6 weeks or so when there was talk about ATI being faster than nvidia, and someone ought to develop an app based on the ATI cards... Come on speedimic, you're missing the fun :P ____________ | |
| ID: 13981 | Rating: 0 | rate:
| |
ATM I'm missing the money... Just got my '83 BMW M3 out of winter sleep - gotta invest in fuel now. ;-) ____________ mic. | |
| ID: 13983 | Rating: 0 | rate:
| |
Awww, and there's me forgoing the lens I've been lusting for to buy plastic bricks that can't even autofocus :~p ____________ | |
| ID: 13987 | Rating: 0 | rate:
| |
I know what you mean...fuel (& fun) or everything else. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 13990 | Rating: 0 | rate:
| |
|
| |
| ID: 14006 | Rating: 0 | rate:
| |
0.19d is still under develpment/test for multi-GPUs. I can't say about 0.17 v 0.19/b ____________ | |
| ID: 14017 | Rating: 0 | rate:
| |
The changes to 0.17 is only the CPU (0.19) and GPU detection (0.19b) output to stderr.txt visible under the task details. The calculation stuff is unchanged. Version 0.19d does not use a full core anymore (down to 10% or even less) and was supposed to add some experimental multi GPU support. But the latter isn't really working, yet. | |
| ID: 14025 | Rating: 0 | rate:
| |
Version 0.19d does not use a full core anymore (down to 10% or even less) and was supposed to add some experimental multi GPU support. But the latter isn't really working, yet. In that seems to be taking a little longer than expected ... any chance of a 19d without it so we can get the lower CPU use? | |
| ID: 14045 | Rating: 0 | rate:
| |
Version 0.19d does not use a full core anymore (down to 10% or even less) and was supposed to add some experimental multi GPU support. But the latter isn't really working, yet. I'm on a conference this week. I can't do much here. But 0.19d is floating around already (it is usable, even on a multi GPU setup, it just doesn't use multiple GPUs to the full extent). So if Ice wants he can put it on zslip. He has it already. Alternatively, you can use this link. Be sure to read the included readme.txt! | |
| ID: 14095 | Rating: 0 | rate:
| |
Be sure to read the included readme.txt! I read it
Thanks guys and gals! Much appreciated. ____________ | |
| ID: 14099 | Rating: 0 | rate:
| |
0.19d is floating around already (it is usable, even on a multi GPU setup, it just doesn't use multiple GPUs to the full extent). So if Ice wants he can put it on zslip. He has it already. 0.19d is now on zslip - thanks Cluster Physik. ____________ | |
| ID: 14102 | Rating: 0 | rate:
| |
0.19d is floating around already (it is usable, even on a multi GPU setup, it just doesn't use multiple GPUs to the full extent). So if Ice wants he can put it on zslip. He has it already. Maybe it would be better to advertise it with "lower CPU load" and not multi GPU, as this is not really working. | |
| ID: 14110 | Rating: 0 | rate:
| |
0.19d is floating around already (it is usable, even on a multi GPU setup, it just doesn't use multiple GPUs to the full extent). So if Ice wants he can put it on zslip. He has it already. OK - done ____________ | |
| ID: 14111 | Rating: 0 | rate:
| |
|
Thank you for the update... | |
| ID: 14146 | Rating: 0 | rate:
| |
|
The GPU app is bloody awesome Cluster Physik! Thank you for taking the time to put it together! | |
| ID: 14247 | Rating: 0 | rate:
| |
|
Will this app ever be able to be run on an HD4670? | |
| ID: 14560 | Rating: 0 | rate:
| |
Will this app ever be able to be run on an HD4670? No, the underlying hardware does not support double precision calculations. | |
| ID: 14565 | Rating: 0 | rate:
| |
|
Any news on Linux version? Booting to Windows is like return to 19th Century for me. ;-) | |
| ID: 15897 | Rating: 0 | rate:
| |
|
One more question - how do you prevent other project to soak all cache for WUs? I want to crunch Einstein on CPU along with Milky on GPU, but Milky is limited for 6 WUs/CPU, then Einstein fills up the cache (I have it set for 1 day) and then Milky does not request more work. I had to put No New Work for Einstein and suspend couple of its WUs to keep GPU busy. | |
| ID: 15925 | Rating: 0 | rate:
| |
One more question - how do you prevent other project to soak all cache for WUs? I want to crunch Einstein on CPU along with Milky on GPU, but Milky is limited for 6 WUs/CPU, then Einstein fills up the cache (I have it set for 1 day) and then Milky does not request more work. I had to put No New Work for Einstein and suspend couple of its WUs to keep GPU busy. I have that problem on my quad. I've set the resource share for MW above 50% and limited it to using only 1 CPU to try to overcome this problem. Has worked pretty well, but BOINC still doesn't increase the MW debt sufficiently well since once MW runs out of work it tends to reset the debt. Stupid system.... | |
| ID: 15929 | Rating: 0 | rate:
| |
|
Like TGG, I have my resource share set to a level where it is near 50% on a quad system with the ATI GPU ... MW runs MOST of the time ... but I have "boom and Bust" queues and times when the GPU app is preempted by CPU only tasks of other projects. | |
| ID: 15939 | Rating: 0 | rate:
| |
One more question - how do you prevent other project to soak all cache for WUs? I want to crunch Einstein on CPU along with Milky on GPU, but Milky is limited for 6 WUs/CPU, then Einstein fills up the cache (I have it set for 1 day) and then Milky does not request more work. I had to put No New Work for Einstein and suspend couple of its WUs to keep GPU busy. I have also run into this problem And have tried several different combo's with very little luck..........I found what works best for me is 6.5.0 boinc and the new 19e.....I have it set to run 4 gpu projects and 4 cpu projects and that seems to make everything play nice together.......... | |
| ID: 16003 | Rating: 0 | rate:
| |
One more question - how do you prevent other project to soak all cache for WUs? I want to crunch Einstein on CPU along with Milky on GPU, but Milky is limited for 6 WUs/CPU, then Einstein fills up the cache (I have it set for 1 day) and then Milky does not request more work. I had to put No New Work for Einstein and suspend couple of its WUs to keep GPU busy. I've gotta stop using the development versions in the vain hope that one day it will work right. I can't recall the last time I believed the work fetch policy, resource share and debt system worked like I thought it would/should. Time to send an email to the alpha mailing list. | |
| ID: 16005 | Rating: 0 | rate:
| |
One more question - how do you prevent other project to soak all cache for WUs? I want to crunch Einstein on CPU along with Milky on GPU, but Milky is limited for 6 WUs/CPU, then Einstein fills up the cache (I have it set for 1 day) and then Milky does not request more work. I had to put No New Work for Einstein and suspend couple of its WUs to keep GPU busy. One word: VirtualBox | |
| ID: 16010 | Rating: 0 | rate:
| |
I think that every machine is different and you just have to play around to find the combo that works best for that computer... | |
| ID: 16130 | Rating: 0 | rate:
| |
|
Has anyone else had any issues with .19e? I just started using it today and ran into a problem. I have my pc set to turn off my monitor when I'm idle for 20mins and every time i come back to my pc after this it has rebooted with an error. .19e does seem to run smoother, but i switched back to .19d for the time being. I'm running vista 64 with the 8.12 driver. | |
| ID: 16159 | Rating: 0 | rate:
| |
I just started using it today and ran into a problem. I have my pc set to turn off my monitor when I'm idle for 20mins and every time i come back to my pc after this it has rebooted with an error. Then disable that setting and turn off your monitor by hand ;) | |
| ID: 16174 | Rating: 0 | rate:
| |
|
I do not have any issues with 19.e version, runs smoothly without issues, just Milky server does not send work constantly during the day. My screensaver is set to 10 minutes, WinXP32bit home, ATI 3850, Catalyst 8.12. I am patiently waiting for Linux version. | |
| ID: 16207 | Rating: 0 | rate:
| |
Has anyone else had any issues with .19e? I just started using it today and ran into a problem. I have my pc set to turn off my monitor when I'm idle for 20mins and every time i come back to my pc after this it has rebooted with an error. .19e does seem to run smoother, but i switched back to .19d for the time being. I'm running vista 64 with the 8.12 driver.I am running the same versions as you are and haven't had a problem so far....My monitor is set to turn off in 5 minutes..... | |
| ID: 16360 | Rating: 0 | rate:
| |
|
I have Windows7 machine available with 4870x2 graphics and it is said in the manual that Catalyst driver is not fully installed in Windows7 and needs manual extraction of three files in order to make MW work. It says in Readme file: | |
| ID: 16370 | Rating: 0 | rate:
| |
I have Windows7 machine available with 4870x2 graphics and it is said in the manual that Catalyst driver is not fully installed in Windows7 and needs manual extraction of three files in order to make MW work. It says in Readme file: .. Just use the new Catalyst 9.3 (has official Win7 support). Then you only have to copy and rename the files as described for Cat 9.2. | |
| ID: 16400 | Rating: 0 | rate:
| |
|
Just setting up a box for a friend - and could not resist to try his 4850. :)) | |
| ID: 16834 | Rating: 0 | rate:
| |
|
4850 X2 from saphhire here... Vista64, 9.3 driver.... 0.19e gpu client... no problems... great bang for the buck once enough GPU wus are available. | |
| ID: 17685 | Rating: 0 | rate:
| |
|
I've successfully used the latest official Catalyst 9.5 for Windows 7 64 with my HD 4870. You still need to recreate the same three missing dll files. | |
| ID: 22767 | Rating: 0 | rate:
| |
|
I don't know if it's useful to say that, but a friend tested the optimization with a Radeon HD 4890, and it works very well. 5-8 seconds by workunit. | |
| ID: 22885 | Rating: 0 | rate:
| |
I've successfully used the latest official Catalyst 9.5 for Windows 7 64 with my HD 4870. You still need to recreate the same three missing dll files. Hi people, I have a problem with the last catalyst 9.5 for Win 7 x64. I reinstalled OS from Beta (using 8.12 and x64 ATI GPU app with no serious problems) to RC1 version. But I can´t find any aticalX64 dll in the system after driver installation (only 3 "normal" aticalx dll in the Windows/System 32 folder). I tried make copy and renamed this dll, but all workunits with x64ATI GPU application are crashed. It works only with (the change to) 32b_ATI_SSE2e in the project directory! :/ Response of the OS is worse, than before reinstalling :( and I´m confused, because I tried new re-installing of drivers and OS without progress :( Needs the x64 ATI GPU app the ati&amdcalrt64.dll, ati&amdcalcl64.dll and ati&amdcaldd64.dll in the Windows/System 32 folder? (Win 7 64 bit, Q6600, 6 GB RAM, ATI 4870, cat. 9.5 for Win 7 x64) | |
| ID: 23081 | Rating: 0 | rate:
| |
|
It sounds like you installed the 32-bit version instead as installed the 64-bit version on my system and got the 64-bit .dll's | |
| ID: 23083 | Rating: 0 | rate:
| |
|
Few hours without sleep and the repeated "fresh" installation of Win 7 RC1 x64 and old catalyst 9.1 without copying and renaming dll files have been solved the "x64 GPU ATI app" problem. | |
| ID: 23105 | Rating: 0 | rate:
| |
|
ATI/AMD renamed the CAL libraries with the latest driver release. To get the GPU app running, | |
| ID: 23132 | Rating: 0 | rate:
| |
|
arkayn: this readme text isn´t helpful to me (1 day ago), therefore 2 follow up questions for x64 Win 7 and catalyst 9.5 | |
| ID: 23142 | Rating: 0 | rate:
| |
So triple 4870's are out of the question for now I see :) Ditto! | |
| ID: 26342 | Rating: 0 | rate:
| |
|
I know this thread is old but I didn't know where else to post my problem. | |
| ID: 29510 | Rating: 0 | rate:
| |
I don't understand how this programme works. I have a 4870 and would love to use that to help out but when I put the programme directory (win64) in the Milkyway project directory or copy the files to the project directory the files corrupt. And I don't understand what you are trying to do. You have to unzip the files in the package to the milkyway project directory. What I forgot to mention is that the astronomy_0.19_ATI_x64f file always reports that the three AMD files are missing, no matter where I place them or however many times I copy them to the system32 folder. Where does it report that? Actually you have to copy the three files and rename the copies, so you should have the three amdcal*64.dll as well as three atical*64.dll files in the system32 folder as explained in the readme. If you want to use the 32bit version with your Vista64 than you have to do the copy and rename in the SysWOW64 folder. By the way, look at this thread! | |
| ID: 29511 | Rating: 0 | rate:
| |
|
This is the error I get | |
| ID: 29518 | Rating: 0 | rate:
| |
This is the error I get [..] I see that you don't have the files with the original names in that directory. Running Cat9.2 and up on a 64bit OS you need the three (copied and renamed) amdcal*64.dll files as well as the three original atical*64.dll files. The ones without 64 in the name are the 32bit versions (in case you have not removed the 64 while renaming them). | |
| ID: 29521 | Rating: 0 | rate:
| |
This is the error I get [..] The original 64bit files were never named atical*64.dll, I renamed and added those three files to the directory and it still has had no effect. I've reinstalled the 9.7 drivers and it's had no effect. As I said, I hope the GPU application is updated to include the changes made to the ATI drivers that took place over six months ago. Soon new video cards will be released which will not run on the 8.12 drivers (not without the .ini 'hack'). Until then I will just run MW on my CPU and wait. | |
| ID: 29533 | Rating: 0 | rate:
| |
|
are you installing the 64bit video drivers? I don't think the 32bit cal files should be there unless the 32bit driver was installed. | |
| ID: 29534 | Rating: 0 | rate:
| |
|
It's impossible to install 32bit drivers in a 64bit OS and visa versa, therefore I have installed 64bit drivers in Vista 64. The lack of the numbers 64 when it comes to the driver is just the way AMD's drivers work. | |
| ID: 29545 | Rating: 0 | rate:
| |
|
that's what I thought as well, just thinking aloud. | |
| ID: 29550 | Rating: 0 | rate:
| |
As I said, I hope the GPU application is updated to include the changes made to the ATI drivers that took place over six months ago. Soon new video cards will be released which will not run on the 8.12 drivers (not without the .ini 'hack'). But that change would most certainly break the app on all WinXP machines, as ATI obviously introduced a bug with Cat 9.3 they have still not fixed. And to copy and rename three files is normally not that much of an effort. There are a lot of people running new driver versions with Vista and Win7 ;) | |
| ID: 29560 | Rating: 0 | rate:
| |
As I said, I hope the GPU application is updated to include the changes made to the ATI drivers that took place over six months ago. Soon new video cards will be released which will not run on the 8.12 drivers (not without the .ini 'hack'). Renaming the files isn't hard work but it doesn't work and this is after several Windows and driver reinstallations. The application NEEDS updating! I don't care whether they create two different applications, one for XP and one for Vista/Win 7 but with the advent of the 5870 (which I'm going to buy) Milkey Way at home is going to lose out. I am aware that BOINC are working on ATI recognition and usability through the client application itself but this application by MW is months overdue. | |
| ID: 31192 | Rating: 0 | rate:
| |
As I said, I hope the GPU application is updated to include the changes made to the ATI drivers that took place over six months ago. Soon new video cards will be released which will not run on the 8.12 drivers (not without the .ini 'hack'). I'm not sure why you're referring to "them". The ATI app was written by Gipsel and NOT the MW team, so it's up to him to do it or not. Besides that, if the MW team could ever come up with an ATI app by themselfs, which i highly doubt ( it's a micacle that they got the cuda thing going, after all), it should be easy for the server scheduler to send a matching app for whatever driver version is installed on the requesting host. The boinc client includes the driver version/CAL version in it's work request ... ____________ Join BOINC United now! | |
| ID: 31206 | Rating: 0 | rate:
| |
Renaming the files isn't hard work but it doesn't work and this is after several Windows and driver reinstallations. The application NEEDS updating! I don't care whether they create two different applications, one for XP and one for Vista/Win 7 but with the advent of the 5870 (which I'm going to buy) Milkey Way at home is going to lose out. The "they" you speak if of NOT the BOINC staff - if it were left up to DA and the bunch it would still be months if not a year out. Crunch3r is the one credited for getting this done . I think Gispel had some input to it, forgive me if I am missing someone here that I am not aware of. But I do know for certain that DA and group had nothing to do with the implementation of ATI/CAL into BOINC core. And the ATI app was not written by the MW staff. As mentioned by Crunch3r, it was Gispel that did this work. It took the MW staff MONTHS to even get a working version for CUDA - and I have to wonder how well that code is really doing. Not well from what I have heard and seen. The MW/CAL app is an optimized app, and in my opinion does not need updating any more than it is. You don't have to run it you know.... There are stock apps that you can crunch with and not have to worry about renaming any files or doing anything special to get them to run. ____________ . | |
| ID: 31229 | Rating: 0 | rate:
| |
The application NEEDS updating! I don't care whether they create two different applications, one for XP and one for Vista/Win 7 but with the advent of the 5870 (which I'm going to buy) Milkey Way at home is going to lose out. What do you want to hear? That I don't care about you not beeing able to copy some lousy files? And I don't NEED to do anything. It was just a voluntary effort from my side, because I got curious how fast it would be. What did I get from that? A load of work and nothing else. I could have spent my time also with something more important. I don't need that some pissed off guy probably just too stupid to follow simple instructions tries to tell me what I have to do. Your case is very simple. Windows tells you it can't find a file. That means the appropriate file is not in the appropriate location. You have to fix that. Go figure! | |
| ID: 31266 | Rating: 0 | rate:
| |
|
readme file :) its our best friend :) | |
| ID: 31267 | Rating: 0 | rate:
| |
And I don't NEED to do anything. It was just a voluntary effort from my side, because I got curious how fast it would be. What did I get from that? A load of work and nothing else. I could have spent my time also with something more important. The work put in by Gipsel and others is awesome and quite rightly he didn't NEED to do it or let any of us benefit from it. Cheers Gipsel and testers etc. You're the best! ____________ | |
| ID: 31289 | Rating: 0 | rate:
| |
What did I get from that? A load of work and nothing else. Though it is of little value, you have my thanks and admiration. For what it is worth, I repeat the thanks ... If for no other reason than it shows that the ATI cards are just as capable and valuable in GPU work as the Nvidia cards. | |
| ID: 31601 | Rating: 0 | rate:
| |
What did I get from that? A load of work and nothing else. Dear Gipsel, you have my thanks and admiration too. Your dedication to this project is really fantastic, without even being in the MW team you seem to give the best support. | |
| ID: 32326 | Rating: 0 | rate:
| |
|
I am a complete newb, and this thread is far too long to read through the entire thing. | |
| ID: 32550 | Rating: 0 | rate:
| |
I am a complete newb, and this thread is far too long to read through the entire thing. Just connect up to Mw like any other project. There are opti apps if you want to use them. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 32553 | Rating: 0 | rate:
| |
|
Well, I found the app in this thread, put it into the right folder I believe (programdata/boinc/projects/milkyway), and BOINC seems to pick it up now... | |
| ID: 32577 | Rating: 0 | rate:
| |
|
nvm, I've been given a better link than the one I found here and will try out a different version of the app/instructions when I get home and am not stuck with RDP. | |
| ID: 32578 | Rating: 0 | rate:
| |
nvm, I've been given a better link than the one I found here and will try out a different version of the app/instructions when I get home and am not stuck with RDP. If you are logged in through RDP the application can't access the graphics card. This is more or less a limitation of Windows (applies to CUDA apps, too) as it uses a virtual graphics card driver for the remote sessions (which doesn't support GPGPU computations of course). The application has to run in the console session. The latest BOINC release (6.10.15) has some code added to detect a remote desktop connection and pauses the GPU application execution. If you have to run it remote you may try VNC (I use UltraVNC) *without* the mirror driver. The responsiveness will be worse, but it works. | |
| ID: 32579 | Rating: 0 | rate:
| |
|
There are a lot of computation errors going around nowadays, about half of each batch of 48WUs on my 'general use' PC ends up that way. Almost none on my crunchers. Doesn't seem to be hurting the rac though, probably because they fail as soon as they start and don't waste much time crunching before failing. | |
| ID: 32587 | Rating: 0 | rate:
| |
|
Alright, got the ATI app working. Was crunching through WU's in 45-60 seconds apiece... right up until it locked up and reset the card :/ | |
| ID: 32588 | Rating: 0 | rate:
| |
|
duplicate entry | |
| ID: 32701 | Rating: 0 | rate:
| |
There are a lot of computation errors going around nowadays, about half of each batch of 48WUs on my 'general use' PC ends up that way. Almost none on my crunchers. Doesn't seem to be hurting the rac though, probably because they fail as soon as they start and don't waste much time crunching before failing. I'm seeing several wu's with computation errors too but not in that great number. I noticed some running version .20, and my GPU would lock up every now and then, hd 4850 1g with catalyst 9.9. so I installed version .20b. but now the lock ups are happening more frequently, so I upgraded catalyst to version 9.10 last night. It only ran a few hours and locked up again. It seems that if they fail right away, then the gpu doesn't lock up. But if they fail after they've been crunching for a few seconds or near the end, it locks up the gpu | |
| ID: 32703 | Rating: 0 | rate:
| |
There are a lot of computation errors going around nowadays, about half of each batch of 48WUs on my 'general use' PC ends up that way. Almost none on my crunchers. Doesn't seem to be hurting the rac though, probably because they fail as soon as they start and don't waste much time crunching before failing. I figured out my own problem. The issue of MW locking up on the gpu had been going on all along. I had been running multiples, 3 @ the same time. I would notice much later that only 2 or 1 were running, then close Boinc and restart. But I had switched over to running only 1 @ a time, and several weeks later I began having the intermittent problem of MW not processing at all as the 1 unit has locked up and cannot release the next to process. I finally realized the two issues were the same issue and started running 2 units at the same time again. | |
| ID: 32731 | Rating: 0 | rate:
| |
|
I've got a 512 MB 4850, running 1 unit at a time, catalyst 9.9, Windows 7 x64, app 20b, seems to be running fine, no lockups that I've seen. | |
| ID: 32771 | Rating: 0 | rate:
| |
I've got a 512 MB 4850, running 1 unit at a time, catalyst 9.9, Windows 7 x64, app 20b, seems to be running fine, no lockups that I've seen. Yes, mine do. ____________ | |
| ID: 32777 | Rating: 0 | rate:
| |
|
Will there be any improved ATI GPU applications planned for near future? I'd like to contribute by running these, but with most of my computers I can't get the app to run without occasional VPU-Recoveries. As you probably know this causes the ATI App to hang up, using 100% of CPU and the time counter on the task/wu increases but progress is halted -> Total waste of nerves, electricity, time etc. | |
| ID: 33988 | Rating: 0 | rate:
| |
|
-Double- | |
| ID: 33989 | Rating: 0 | rate:
| |
|
Seems like 0.20b is at fault here, been running 0.19f for a while without problems... | |
| ID: 34212 | Rating: 0 | rate:
| |
|
any chance this is compatible with my 5770? | |
| ID: 34526 | Rating: 0 | rate:
| |
any chance this is compatible with my 5770? Unfortunately no as the 5700 series does not support double precision. It looks like you are keeping it warm on Collatz though. ____________ | |
| ID: 34529 | Rating: 0 | rate:
| |
|
that sucks, i was hoping to put my new card to use. yeah collatz seems to be the only project that supports ati at the moment. | |
| ID: 34530 | Rating: 0 | rate:
| |
|
Hi guys, | |
| ID: 34572 | Rating: 0 | rate:
| |
|
Forget that last msg. I've somehow pulled a rabbit from the hat and it works now, or at least seems to. God knows why it wasn't workin the other week. | |
| ID: 34575 | Rating: 0 | rate:
| |
Message boards :
Application Code Discussion :
GPU app teaser