Author |
Message |
|
If the app_config is not working try this here:
<exclude_gpu>
<url>http://srbase.my-firewall.org/sr5/</url>
<device_num>1</device_num>
<type>NVIDIA|ATI</type>
<app>GPU72</app>
</exclude_gpu>
change the type what you have in your PC and put this code in the option section of cc_config
This is working for me. One GPU is running gpu72, the other GPU is running a task from another project.
____________
Reno, NV
Team: SETI.USA
|
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
If the app_config is not working try this here:
<exclude_gpu>
<url>http://srbase.my-firewall.org/sr5/</url>
<device_num>1</device_num>
<type>NVIDIA|ATI</type>
<app>GPU72</app>
</exclude_gpu>
change the type what you have in your PC and put this code in the option section of cc_config
This is working for me. One GPU is running gpu72, the other GPU is running a task from another project.
is this working too?
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config> |
|
|
|
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? |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
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.
I think this is the app itself, its always running on Device 0, so we need to get rid of the second Device and let it free for other projects. |
|
|
|
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? |
|
|
PDWSend message
Joined: 15 Oct 15 Posts: 41 Credit: 1,322,631,594 RAC: 3,729,537 |
In case it helps now, or in the future !
I believe BOINC numbers GPUs in the order it receives information about them from CAL, CUDA or OpenCL drivers. (This from the BOINC forum a couple of years ago.)
I do not know if the mfakto/mfaktc when given a device number is then using the BOINC GPU numbering or a number assigned by the OS when it enumerates the GPUs.
Just putting it out there :) |
|
|
|
In case it helps now, or in the future !
I believe BOINC numbers GPUs in the order it receives information about them from CAL, CUDA or OpenCL drivers. (This from the BOINC forum a couple of years ago.)
I do not know if the mfakto/mfaktc when given a device number is then using the BOINC GPU numbering or a number assigned by the OS when it enumerates the GPUs.
Just putting it out there :)
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. |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config>
Is this working for Multi-GPU? If not I will remove it and will only use the cc_config solution, next step is the opencl error thing. |
|
|
|
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config>
Is this working for Multi-GPU? If not I will remove it and will only use the cc_config solution, next step is the opencl error thing.
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. |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config>
Is this working for Multi-GPU? If not I will remove it and will only use the cc_config solution, next step is the opencl error thing.
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.
ok, thx, but I dont want to keep the 2nd GPU busy (blocked) and not free for another project |
|
|
PDWSend message
Joined: 15 Oct 15 Posts: 41 Credit: 1,322,631,594 RAC: 3,729,537 |
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config>
You should change the line:
<project_max_concurrent>1</project_max_concurrent>
to be...
<max_concurrent>1</max_concurrent>
This will restrict GPU72 to only running 1 task but other SRBase CPU tasks can be run at the same time.
The <project_max_concurrent> x </project_max_concurrent> tags don't go within the <app> </app> section. |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
<app_config>
<app>
<name>GPU72</name>
<project_max_concurrent>1</project_max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.01</cpu_usage>
</gpu_versions>
</app>
</app_config>
You should change the line:
1
to be...
1
This will restrict GPU72 to only running 1 task but other SRBase CPU tasks can be run at the same time.
The x tags don't go within the section.
ok, changed it back in FAQs |
|
|
|
Can anyone post a app_config.xml file that works successfully with a AMD GPU? (Ubuntu, Intel CPU).
I managed to get mfakto running standalone with:
./mfakto-x64 -d 1
Yet, every task in boinc is crashing. As many have reported.
My current app_config.xml:
<app_config>
<app>
<name>GPU72</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>GPU72</app_name>
<plan_class>opencl_ati_101</plan_class>
<cmdline>-d 1</cmdline>
</app_version>
</app_config>
|
|
|
|
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> |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
Can you also try with
-d 0
-d 10
-d 11
test with wrapper app, change the job....xml to job.xml and start the wrapper. |
|
|
|
Can you also try with
-d 0
-d 10
-d 11
test with wrapper app, change the job....xml to job.xml and start the wrapper.
How do you start the wrapper standalone?
Could you copy your commandline?
I've tried with chmod, but time and time again returns "no file or directory".
The other -d types where not working. I've also tried every combination in the app_config.xml file with the cmdline, still not working... |
|
|
|
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?
I'm successfully using this in my cc_config to exclude the second GPU in all of my two-GPU systems, so that one doesn't go to waste when running GPU72. I am running another project on the second GPU in those rigs.
____________
|
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
Can you also try with
-d 0
-d 10
-d 11
test with wrapper app, change the job....xml to job.xml and start the wrapper.
How do you start the wrapper standalone?
Could you copy your commandline?
I've tried with chmod, but time and time again returns "no file or directory".
The other -d types where not working. I've also tried every combination in the app_config.xml file with the cmdline, still not working...
try this:
./wrapper_26012-v2_x86_64-pc-linux-gnu
The job.xml file must be in the same folder
here is a snipped from the help about the -d command
-d specify to use OpenCL platform number x and device number y in this program |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
Send message
Joined: 2 Jan 13 Posts: 7492 Credit: 43,876,295 RAC: 26,609 |
If someone is able to compile the mfaktc app v0.21 for Mac let me know:
https://www.mersenneforum.org/showthread.php?t=12827&page=254
Sourcecode:
https://download.mersenne.ca/mfaktc/mfaktc-0.21 |
|
|
|
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?
I'm successfully using this in my cc_config to exclude the second GPU in all of my two-GPU systems, so that one doesn't go to waste when running GPU72. I am running another project on the second GPU in those rigs.
Yes, on NVIDIA. Not on AMD. |
|
|