Restricting Versions that can Run?
log in

Advanced search

Message boards : Windows : Restricting Versions that can Run?

Author Message
EPAstor
Send message
Joined: 24 Jan 10
Posts: 4
Credit: 19,194,722
RAC: 0
Message 14714 - Posted: 11 Sep 2012, 4:38:14 UTC

So - I'm still getting WUs for old versions of the GPU code. Especially for the mini_collatz units... I keep getting CUDA 2.3 units. This is a problem - because of BOINC's stupidity, the so-called "threadsafe" issue, and the fact that I do game, so I keep my nVidia drivers up to date.

If I keep getting these WUs, I cannot afford to let this project use my GPU... it makes my system much slower, and occasionally unstable. (As far as I can tell, the 560 Ti's are especially vulnerable to this issue.)

Is there any way to restrict the WUs I receive to be CUDA 4.2 or OpenCL-based only? (One option would be to ban earlier certain Collatz applications from my system.) If not, then I'll have to disable my GPU contributions to this project for good - and I hate to have to do that!

Profile mikey
Avatar
Send message
Joined: 11 Aug 09
Posts: 3242
Credit: 1,688,181,715
RAC: 6,053,128
Message 14716 - Posted: 11 Sep 2012, 11:22:28 UTC - in response to Message 14714.

So - I'm still getting WUs for old versions of the GPU code. Especially for the mini_collatz units... I keep getting CUDA 2.3 units. This is a problem - because of BOINC's stupidity, the so-called "threadsafe" issue, and the fact that I do game, so I keep my nVidia drivers up to date.

If I keep getting these WUs, I cannot afford to let this project use my GPU... it makes my system much slower, and occasionally unstable. (As far as I can tell, the 560 Ti's are especially vulnerable to this issue.)

Is there any way to restrict the WUs I receive to be CUDA 4.2 or OpenCL-based only? (One option would be to ban earlier certain Collatz applications from my system.) If not, then I'll have to disable my GPU contributions to this project for good - and I hate to have to do that!


I THINK you can do it thru an "app_info.xml" file or since you are using Boinc version 7.0.28 just go into the Boinc Manager down by the clock and go to the Tools, computing preferences section and then you will see "exclusive applications". In there you can set Boinc so that it stops while you are gaming. Then when you are done gaming Boinc will automatically start back up again. I have never used that setting so you may have to research it or do some trail and error to figure out what you need to put in there, but I am guessing the exe file that starts your game.

EPAstor
Send message
Joined: 24 Jan 10
Posts: 4
Credit: 19,194,722
RAC: 0
Message 14747 - Posted: 21 Sep 2012, 7:38:12 UTC - in response to Message 14716.

That's... not exactly what I'm looking for, sadly. I'm trying to prevent my computer running certain types of WUs EVER, not tell BOINC to stop while I'm gaming. The highly misleading functionality in BOINC known as the "threadsafe" issue leaves nVidia drivers in a slow and/or unstable state from when a "non-safe" application is run on the GPU until the next reboot.

So... is there any way for me to restrict my computer to only run the CUDA 4.2 or OpenCL-based GPU work units?

Profile mikey
Avatar
Send message
Joined: 11 Aug 09
Posts: 3242
Credit: 1,688,181,715
RAC: 6,053,128
Message 14749 - Posted: 21 Sep 2012, 13:10:12 UTC - in response to Message 14747.

That's... not exactly what I'm looking for, sadly. I'm trying to prevent my computer running certain types of WUs EVER, not tell BOINC to stop while I'm gaming. The highly misleading functionality in BOINC known as the "threadsafe" issue leaves nVidia drivers in a slow and/or unstable state from when a "non-safe" application is run on the GPU until the next reboot.

So... is there any way for me to restrict my computer to only run the CUDA 4.2 or OpenCL-based GPU work units?


Maybe thru an app_info.xml file? A line in the MilkyWay app_info.xml file says:
<name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name>.

I do not have one for Collatz but it should do the same thing, meaning you could tell it what file to run to crunch.

zzuupp
Send message
Joined: 14 Mar 10
Posts: 128
Credit: 347,767,607
RAC: 37,025
Message 14769 - Posted: 25 Sep 2012, 1:41:07 UTC - in response to Message 14749.

here's my app-info. However, it is only for the 'big' tasks.


<app_info>
<app>
<name>collatz</name>
</app>
<file_info>
<name>collatz_3.14_windows_intelx86__cuda42.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_42_9.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>collatz</app_name>
<version_num>311</version_num>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.011</avg_ncpus>
<max_ncpus>1</max_ncpus>
<flops>1.0e11</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<cmdline>K128 I524288 S1</cmdline>
<file_ref>
<file_name>collatz_3.14_windows_intelx86__cuda42.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_42_9.dll</file_name>
</file_ref>
</app_version>
</app_info>


Post to thread

Message boards : Windows : Restricting Versions that can Run?


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.