1) Message boards : Number crunching : Tips for making AMD 6970 run faster (Message 66437) Posted 13 May 2017 by v10rider Post: Does anybody have tips for making the old AMD 6970 run faster. I'm running Win 10 with the latest AMD drivers. I've tried running 1 to 4 apps and it doesn't seem to make a difference. I've tried staggering the tasks so they don't line up but that doesn't make a difference either, plus they all end up at 20% increments eventually. The GPU goes to 100% for a few seconds then goes to 0% for 20 seconds while the CPU maxes out. I have a GTX 470 in the same machine and it stays at 100% the whole time with no breaks. I know not the greatest for MW but I still use it. Thanks for any help.

2) Message boards : Number crunching : dual 6970s (Message 66162) Posted 6 Feb 2017 by v10rider Post: After a long absence from MW since my 6970 didn't work I figured I'd give it another shot. It seem to be working now but my GPU seems to run at 98% for 5 seconds then off for 5. Is there something I can do to correct this, I'm on a Windows 10 64 bit machine?

3) Message boards : Number crunching : OpenCL video card assignment issue (Message 53068) Posted 11 Feb 2012 by v10rider Post: Thanks again arkayn, your opencl app and app_info are working great so far. I just hope it wasn't a mistake upgrading to Boinc 7.

4) Message boards : Number crunching : OpenCL video card assignment issue (Message 52999) Posted 10 Feb 2012 by v10rider Post: Thanks arkayn but I only have use AMD checked, use CPU and NVIDIA are unchecked. I may have to try the app_info route.

5) Message boards : Number crunching : OpenCL video card assignment issue (Message 52996) Posted 10 Feb 2012 by v10rider Post: I run both a GTX470 and AMD6970 in the same machine. I use the nvidia for SETI(or others when not working) and the AMD for MW. However with the new opencl WU's they are getting assigned to the nvidia card and the 6970 sits idle. Is there a way to not download the opencl wu's or is there another way to solve this issue?

6) Message boards : Number crunching : Is Anyone Addressing This Constant Computation Error Problem? (Message 49274) Posted 14 Jun 2011 by v10rider Post: I think I'll be turning off MW for a while as I'm getting too many 'Error While Computing' and 'Not in DB' WU's. I can't tell what the ratio of good to bad WU's is because they disappear so quickly.

7) Message boards : Number crunching : ATI 6970 & 6850 Problem (Message 46287) Posted 19 Feb 2011 by v10rider Post: Thanks for the info. I just want to avoid the 6850 sitting idle while the 6970 crunches 2 Milkyway work units at once which is slower than running 2 units sequentially. The 6850 could be working on Collatz or DNET at the same time. I'd also rather not have the GPUs run at 60-70% when running a DNET work unit. Again that is no faster than one GPU running at 99% like it usually does. Only Collatz works properly(in my view) crunching 2 separate WU utilizing 99% of each GPU.

8) Message boards : Number crunching : ATI 6970 & 6850 Problem (Message 46283) Posted 18 Feb 2011 by v10rider Post: Is there a way designate GPU0(6970) as my Milkyway card and GPU1(6850) so that it runs everything else ie Collatz and DNETC. Currently DNET uses both at the same time but only using about 60% of each or Milkyway runs 2 WU on the 6970 while the 6850 sits idle. I used GPUZ to check. BTW it takes 75 seconds to run one wu at a time but it takes 165 seconds to run 2 at a time. What can I add to the cc_config file to fix this? Thanks

©2024 Astroinformatics Group