1)
Message boards :
Number crunching :
GEFORCE RTX 20 SERIES
(Message 8089)
Posted 24 Jan 2019 by [AF>FAH-Addict.net]toTOW Post: OpenCL application (1.05) will be faster for modern nVidia GPUs ... you just have to wait until the server decides to send you this application instead of the old CUDA one. |
2)
Message boards :
Number crunching :
How to avoid CUDA application ?
(Message 8088)
Posted 24 Jan 2019 by [AF>FAH-Addict.net]toTOW Post: It finally decided to send OpenCL work to this machine ... but I don't know why ... |
3)
Message boards :
Number crunching :
How to avoid CUDA application ?
(Message 8084)
Posted 6 Jan 2019 by [AF>FAH-Addict.net]toTOW Post: I have a machine that won't run any CUDA applications, but work fine with OpenCL ones, but the project keeps trying to send the old cuda31 work units (1.03 application). How to tell the server to avoid them and send only the newest OpenCL 1.05 application work units ? My other machines which are quite similar (all Windows 10 and NV GPUs) are getting these OpenCL WUs fine. |
4)
Message boards :
Number crunching :
Beta Android app : validation inconclusive
(Message 6182)
Posted 14 Sep 2014 by [AF>FAH-Addict.net]toTOW Post: My Android device (Galaxy Nexus) has just completed its firts WU, but it is in validation inconclusive state :( I don't see what's wrong in the stderr output, so if someone whould like to look at it, here's the link to the host : http://moowrap.net/show_host_detail.php?hostid=27376 |
5)
Message boards :
News :
New app v1.4 with OpenCL support deployed
(Message 6181)
Posted 14 Sep 2014 by [AF>FAH-Addict.net]toTOW Post: Tip for (any) OpenCL app on ATI cards : the GPU usage is usually maxed when the application runs with fixed CPU affinity setting. You can do this manually with Windows Task Manager by checking only one thread in affinity setting. If you see performance improvement, this trick can be automanted with Bill2's Process Manager which allows the création of rules to automatically apply settings when a given process is started. |
6)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6168)
Posted 8 Sep 2014 by [AF>FAH-Addict.net]toTOW Post: Finally, it works ! See announcement thread here : http://moowrap.net/forum_thread.php?id=369 |
7)
Message boards :
News :
New app v1.4 with OpenCL support deployed
(Message 6167)
Posted 8 Sep 2014 by [AF>FAH-Addict.net]toTOW Post: It's doing fine on my R9 290X ! :) I had to set up CPU affinities manually to achieve best efficiency, like I hade to do with all OpenCL applications ... |
8)
Message boards :
News :
We have badges!
(Message 6149)
Posted 4 Sep 2014 by [AF>FAH-Addict.net]toTOW Post: It should work, the distributed.net client does : dnetc v2.9111-520-GTR-12082118 for OpenCL on Win32 (WindowsNT 6.1). |
9)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6128)
Posted 29 Aug 2014 by [AF>FAH-Addict.net]toTOW Post: Since the server move is over, can we get our OpenCL application for modern ATI GPUs ? |
10)
Message boards :
News :
We have badges!
(Message 6127)
Posted 29 Aug 2014 by [AF>FAH-Addict.net]toTOW Post: Phil1966, for this project, get an ATI GPU. This project has always been a playground for ATI, which are performing much better than NV ... |
11)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6038)
Posted 29 May 2014 by [AF>FAH-Addict.net]toTOW Post: This project looks so dead ... were is the developer ? |
12)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6032)
Posted 6 May 2014 by [AF>FAH-Addict.net]toTOW Post: Glad it worked for you ... But it's too bad that no one cares about the Hawaii GPUs :( |
13)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6020)
Posted 22 Apr 2014 by [AF>FAH-Addict.net]toTOW Post: mikey> The SDK has been useless for years now since AMD APP drivers are included in Catalyst packages. Colltaz runs fine on this GPU without any special trick, and I've been able to run PrimeGrid (PPS Sieve, GFN and GFN WR) and MilkyWay with the use of an app_info ... John> in your situation, the problem is different : you have been able to start the client ! You should be able to run without issues by replacing your dnetc518-win32-x86-stream.exe file by the dnetc.exe (OpenCL version) included in this package : http://http.distributed.net/pub/dcti/current-client/dnetc-win32-x86-opencl.zip You can use my app_info file to use it. You'll have to edit the job-ati14-1.00.xml file with the following data assuming you keep the dnetc.exe file name : <job_desc> <task> <application>dnetc.exe</application> <checkpoint_filename>chkpoint</checkpoint_filename> <command_line>-ini dnetc.ini -runoffline -multiok=1</command_line> </task> </job_desc> This is the method for HD79xx that I used for my try on my R9 290X ... Unfortunately, all these tricks doen't work on the R9 290X :'( |
14)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6016)
Posted 21 Apr 2014 by [AF>FAH-Addict.net]toTOW Post: mikey> of course, and if it had worked, I wouldn't bother with an app_info ! John> yeah, same for me, the distributed.net client runs fine on the card, it's just Moo that doesn't like the card :( |
15)
Message boards :
Number crunching :
Cuda 6 -> Multi-GPU Scaling support for Moo! ?
(Message 6012)
Posted 20 Apr 2014 by [AF>FAH-Addict.net]toTOW Post: Moo can't do anything on supporting new features from APIs since they're not the developpers of the application that actually does the computation. You should ask to http://www.distributed.net/ developpers instead ... |
16)
Message boards :
Number crunching :
Any chance to get support of R9 290X on this project ?
(Message 6011)
Posted 20 Apr 2014 by [AF>FAH-Addict.net]toTOW Post: I tried to make my R9 290X run on this project with an app_info, but it won't ... I used an app_info based on one for a 79xx card I found on this forum, but it doesn't work at all. I get work, but it won't start with this error : 20/04/2014 23:21:03 | Moo! Wrapper | [error] Missing coprocessor for task dnetc_r72_1398013104_2_32_0; aborting I get the error before it even start to download the WU :( For reference, here is the app_info I use : <app_info> <app> <name>dnetc</name> <user_friendly_name>Distributed.net Client</user_friendly_name> </app> <file_info> <name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</name> <executable/> </file_info> <file_info> <name>dnetc.exe</name> <executable/> </file_info> <file_info> <name>dnetc-gpu-1.3.ini</name> </file_info> <file_info> <name>job-ati14-1.00.xml</name> </file_info> <app_version> <app_name>dnetc</app_name> <version_num>103</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14</plan_class> <api_version>7.2.42</api_version> <file_ref> <file_name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>dnetc.exe</file_name> <copy_file/> </file_ref> <file_ref> <file_name>dnetc-gpu-1.3.ini</file_name> <open_name>dnetc.ini</open_name> <copy_file/> </file_ref> <file_ref> <file_name>job-ati14-1.00.xml</file_name> <open_name>job.xml</open_name> <copy_file/> </file_ref> <coproc> <type>ATI</type> <count>1</count> </coproc> </app_version> </app_info> It would be a good idea to add OpenCL support to this project to make thing much easier for cruncher since Distributed.net has been providing an official OpenCL client for more than 6 month ... Any idea to make my card work until we hear some news from the dev of this project ? |
17)
Message boards :
Number crunching :
OpenCL versus Stream/CAL on distributed.net / Moo client.
(Message 4053)
Posted 25 Oct 2012 by [AF>FAH-Addict.net]toTOW Post: I didn't run it under BOINC. I did my tests with the distributed.net clients. |
18)
Message boards :
Number crunching :
OpenCL versus Stream/CAL on distributed.net / Moo client.
(Message 3988)
Posted 14 Oct 2012 by [AF>FAH-Addict.net]toTOW Post: There is an upcoming distributed.net OpenCL client in the pipe to support HD7k GPUs. I tested it on my HD6950 (800 MHz, but with reactivated shaders like on HD6970) with 12.6 drivers and I have one good news and one bad news. The good one : performances are identical with Stream/CAL client and with OpenCL one :) Here are the numbers with Stream/CAL client : [Oct 14 21:36:18 UTC] RC5-72: Summary: 6 packets (332.00 stats units) And then with OpenCL one : [Oct 14 21:52:08 UTC] RC5-72: Summary: 6 packets (351.00 stats units) The bad news is : like any other OpenCL application that I know about, it requires one free CPU core to feed the GPU or you'll get pathetic performances :/ With OpenCL client, with BOINC client shut down : [Oct 14 21:52:22 UTC] RC5-72: using core #0 (CL ANSI 1-pipe). And with BOINC client running on the CPU (8 SIMAP cores), with OpenCL client still : [Oct 14 21:54:04 UTC] RC5-72: using core #0 (CL ANSI 1-pipe). This time, BOINC client shut down and with Stream/CAL client : [Oct 14 21:58:01 UTC] RC5-72: using core #0 (IL 4-pipe c). And finally, with BOINC client running (8 SIMAP cores),with Stream/CAL again : [Oct 14 21:58:46 UTC] RC5-72: using core #0 (IL 4-pipe c). I guess you'll have to set up the OpenCL application in Moo to run with 1 CPU + x GPUs ... |
19)
Message boards :
Wish list :
Priority management in Windows
(Message 1306)
Posted 1 Nov 2011 by [AF>FAH-Addict.net]toTOW Post: Since I installed 11.10 drivers, the client is no longer using my CPU ... :) I hope this issue is definitely behind us. |
20)
Message boards :
Wish list :
Priority management in Windows
(Message 1222)
Posted 21 Oct 2011 by [AF>FAH-Addict.net]toTOW Post: Doing this in the Task Manager is something Boinc probably won't support, Boinc is a process designed to use UNUSED processor cycles, not all the cycles it can to the exclusion of anything else. Boinc was never designed to be used on 'Boinc only' machines. We users do that on our own and the Developers actually discourage that when asked. Now tweaking the project, as Teemu showed everyone how to do, is okay but in the Windows Task Manager probably not. You can always do it manually but everytime you start a new workunit you have to do it again, as it resets after each one is completed. I'm using Bill2's Process Manager : I created a rule on the name of the client, so everytime it starts, B2PM bump the priority to normal automatically :) |