| log in |
|
41)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5972)
Posted 30 Mar 2020 by bluestang As long as you only have 1 AMD GPU, then: <app_config> <app> <name>GPU72</name> <max_concurrent>1</max_concurrent> <gpu_versions> <gpu_usage>1</gpu_usage> <cpu_usage>0.1</cpu_usage> </gpu_versions> </app> </app_config> |
|
42)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5967)
Posted 30 Mar 2020 by bluestang
What do you mean by working? 1 WU running on both GPUs?...then no. But you still need it so it doesn't run 2 WUs on 1 GPU. |
|
43)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5965)
Posted 30 Mar 2020 by bluestang In case it helps now, or in the future ! Doesn't matter, as no matter how you configure it in cc_config or app_config it ignores what you tell it. I've tried 0, 1, 2, etc., forward and backwards and upside down with the same result...only the 1st device in the system is running a WU. At least for AMD GPUs. NVIDIA is another matter all together. |
|
44)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5963)
Posted 30 Mar 2020 by bluestang Well, then that stinks because I don't want it to run on my 1st GPU (7950) as it lags big time then. That is why I have the Vega 64 as my 2nd GPU so it can run full boar on it without any concerns of using that PC for other things. This is the only project I've ran that has ever done this. Never had an issue with any other GPU project and telling it what GPU to run on or not to run on. EDIT: Also, I don't think anyone here who says they are running 1 task/WU on both GPUs actually are. I have yet to see it happen running on NVIDIA like it was state to. If it's always running on 1st device, then how can it possible run simultaneously on the 2nd device as well for the same WU? |
|
45)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5961)
Posted 30 Mar 2020 by bluestang On one of my systems I have a HD7950 (Dev 0) and a Vega 64 (Dev 1). If I include the following in the options section of my cc_config.xml file: <exclude_gpu>
<url>http://srbase.my-firewall.org/sr5/</url>
<type>ATI</type>
<device_num>0</device_num>
<app>GPU72</app>
</exclude_gpu> That should tell it to ignore my 7950 (Dev 0) and run on my Vega 64. However, that is not the case. It still runs on the 2st device no matter what. The status column in BOINC manager says it's running on Device 1 like the cc_config.xml tells it to, but according to GPU utilization in both GPU-Z and HWiNFO it is still running on 1st device. EDIT: So by default nature of the app, it will always use the 1st device no matter what it is told in cc_config or app_config it seems? At least on AMD GPUs. NVIDIA is a different story I think? |
|
46)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5958)
Posted 29 Mar 2020 by bluestang Ok, thanks. Also, appreciate the quick replies from you. Now, take a few days off to relax and then get back to work fixing the app lol :) |
|
47)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5956)
Posted 29 Mar 2020 by bluestang Reb, What about on the client side? |
|
48)
Message boards :
News :
Trial Factoring - new subproject (beta)
(Message 5951)
Posted 29 Mar 2020 by bluestang Is there a bug or something where you can't use more than 1 GPU in a system? This doesn't work like that right now it seems. I'll post in the other from now on about any issues I have. |
|
49)
Message boards :
Number crunching :
Trial Factoring tests
(Message 5949)
Posted 29 Mar 2020 by bluestang "-d c" on AMD GPUs will error out in a couple seconds. It does not work. Also, "-d 0" or "-d 1" do nothing on AMD GPUs in my system (2x RX 580) as to which GPU to use. It doesn't even use the 1st GPU in the system. The app is using the 2nd GPU. There are serious issues/limitations with this app. Especially for AMD GPUs. Also, I have yet to have any of the above command line switches do anything for NVIDIA GPUs either as far as letting the app run 1 WU on both GPUs. It doesn't work. This app needs to be set up to run 1 WU per GPU plain and simple and its not for some reason. I'm not bitching really, I'm just trying to give info to get this sorted. |
|
50)
Message boards :
Number crunching :
Trial Factoring
(Message 5923)
Posted 29 Mar 2020 by bluestang Dear bluestang I am cool. You're reading it wrong. I'm trying to help get this figured out. It was said that the app will use both GPUs to run 1 WU and it wasn't and I'm trying to help figure out why. It's nothing against Rebirther, so don't make it so. Either way, I figured out how to run on both cards by using my own method. After I run out of Seti WUs I'll be back to kick some tail :) |
|
51)
Message boards :
Number crunching :
Trial Factoring
(Message 5919)
Posted 28 Mar 2020 by bluestang Wrong again. -d 1 option does nothing on my 2x 1660ti setup. Only 1 GPU is being utilized by the app. And it is not even the 1st GPU in my system being used...it is the 2nd GPU. Makes no sense at all. EDIT: The -d command only tells the app what GPU to use. It does nothing for running 1 WU on 2 GPUs like is being said in previous posts in this thread. |
|
52)
Message boards :
Number crunching :
Trial Factoring
(Message 5916)
Posted 28 Mar 2020 by bluestang Mine were in the correct locations. |
|
53)
Message boards :
Number crunching :
Trial Factoring
(Message 5914)
Posted 28 Mar 2020 by bluestang Nope, no errors. Both HWiNFO and Afterburner show the 1st GPU deivce 0 being ignored/not used and device 1 being used in my 2x 1660ti setup. Only device 1 shows any utilization in those 2 programs. |
|
54)
Message boards :
Number crunching :
Trial Factoring
(Message 5912)
Posted 28 Mar 2020 by bluestang Yeah, that's not going to work. I basically had that in my app_config and cc_config anyway. Nothing there tells the app to use all GPUs on 1 WU. Only to run 1 WU at a time per GPU and 1 WU max per project. The app is not doing it's job properly by not using all GPUs towards 1 WU on NVIDIA. I'm also not even sure it knows which device to even use as in one system (NVIDIA) its using device 1, not device 0. And in another system its using device 0, not device 1. You would think it would use the 1st device 0 by default. Both have identical 2x GPUs per system. |
|
55)
Message boards :
Number crunching :
Trial Factoring
(Message 5910)
Posted 28 Mar 2020 by bluestang Yes. |
|
56)
Message boards :
Number crunching :
Trial Factoring
(Message 5908)
Posted 28 Mar 2020 by bluestang Lovely, So I have to tell the app how to run my machine properly instead of the app telling my machine how to run properly. You have an app_config.xml template for this I could use? |
|
57)
Message boards :
Number crunching :
Trial Factoring
(Message 5906)
Posted 28 Mar 2020 by bluestang Well, sorry but that's just lame. Both, does it on both AMD and NVIDIA systems with 2 GPUs in each. Shows 2 tasks running but only 1 GPU with utilization. On Windows machines: http://srbase.my-firewall.org/sr5/hosts_user.php?userid=2080 |
|
58)
Message boards :
Number crunching :
Trial Factoring
(Message 5904)
Posted 28 Mar 2020 by bluestang Well, sorry but that's just lame. It makes the other GPU not usable by other projects because BOINC thinks it's in use even thought it isn't. |
|
59)
Message boards :
Number crunching :
Trial Factoring
(Message 5902)
Posted 28 Mar 2020 by bluestang Makes no sense about no multi-GPU support. 1 WU per GPU shouldn't be this hard. Every other project that uses GPU can do it. And I don't see both GPU's working on 1 WU like the FAQ shows for NVIDIA, 1 is idle. So what's the problem here? |
|
60)
Message boards :
News :
Trial Factoring - new subproject (beta)
(Message 5900)
Posted 28 Mar 2020 by bluestang Is there a bug or something where you can't use more than 1 GPU in a system? Any of my systems with dual GPU setups are running 2 tasks at once, but on 1 GPU only. Second GPU is idle. Does this on both AMD and NVIDIA GPUs. |