Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Help Conquer Cancer Thread: GPU Optimisations |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 198
|
Author |
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: |
The NEW version of the Boinc Server Software let's you do it thru a cc_config.xml file. I don't know what version WCG is using but suspect it might be a pain to upgrade due to all the heavy mods they have done. MOST projects modify the server software for various reasons. I can't find anything about such an option for cc_config.xml, and it seems strange if a client-config-option depends on BOINC's server-version... "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
Cheers, that would be much appreciated. Here is an app_info for GPU and CPU tasks. If you're currently running GPU tasks with an app_info you should finish them first or you'll lose them when you change the app_info file. Shut down BOINC and then remove the app_info file you're using now. Restart BOINC without any app_info file and let it download some GPU and CPU tasks. You must do this for it to work. After you do that shut down BOINC, add the new app_info and restart. You should be good. The only thing that might be a problem is the version # of the CPU tasks. If it's 7.05 like the GPU tasks the your good. Check before you put the app_info file into the project directory. If it's different you'll have to edit the app_info to the proper version. This is the portion you'll have to change from the very bottom of the file only. Pay attention to where decimal points go and don't go. <app_version> <app_name>hcc1</app_name> <version_num>705 </version_num> Change here if needed <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3231932486.733310</flops> <api_version>6.13.0</api_version> <file_ref> <file_name>wcg_hcc1_img_7.05 _windows_intelx86</file_name> Change here if needed <main_program/> </file_ref> </app_version> </app_info> HERE IS THE COMPLETE APP_INFO FILE. <app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.5</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3231932486.733310</flops> <api_version>6.13.0</api_version> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86</file_name> <main_program/> </file_ref> </app_version> </app_info> Let me know how it goes.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
<coproc> @nanoprobe:<type>ATI</type> <count>.5</count> </coproc> Two(2) simul GPU-WUs would appear to be 'safe', and ... <comment> Something tells me that, like how overclocking 'evolved', so will the use of an app_info for tweaking (and not for 'anonymous' platform) purposes. There, rather than trying to suppress the activity, it is better to guide the activity towards safe use. On that note, I propose that WCG come up with a guide showing how many simul GPU-WUs a GPU can 'safely' take -- and add this information to the GPU-cards-known-to-work table. Like with overclocking, there should be a warning note appended to that proposed guide. </comment> ; |
||
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: |
I wouldn't want WCG to take on that responsibility considering every setup is different and "safe" is subjective to the situation. There isn't a one set and forget for each card.
---------------------------------------- |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
I wouldn't want WCG to take on that responsibility considering every setup is different and "safe" is subjective to the situation. There isn't a one set and forget for each card. Agree. There are just too many hardware/software variables to consider. Let the end user determine what works best for them.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges: |
Thanks for sharing your app_info.xml, nanoprobe. I'll work with it tomorrow (later today) once my bufffer empties.
----------------------------------------Thanks again Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges: |
Cheers, that would be much appreciated. Here is an app_info for GPU and CPU tasks. If you're currently running GPU tasks with an app_info you should finish them first or you'll lose them when you change the app_info file. Shut down BOINC and then remove the app_info file you're using now. Restart BOINC without any app_info file and let it download some GPU and CPU tasks. You must do this for it to work. After you do that shut down BOINC, add the new app_info and restart. You should be good. The only thing that might be a problem is the version # of the CPU tasks. If it's 7.05 like the GPU tasks the your good. Check before you put the app_info file into the project directory. If it's different you'll have to edit the app_info to the proper version. This is the portion you'll have to change from the very bottom of the file only. Pay attention to where decimal points go and don't go. <app_version> <app_name>hcc1</app_name> <version_num>705 </version_num> Change here if needed <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3231932486.733310</flops> <api_version>6.13.0</api_version> <file_ref> <file_name>wcg_hcc1_img_7.05 _windows_intelx86</file_name> Change here if needed <main_program/> </file_ref> </app_version> </app_info> HERE IS THE COMPLETE APP_INFO FILE. <app_info> <app> <name>hcc1</name> <user_friendly_name>Help Conquer Cancer</user_friendly_name> </app> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name> <executable/> </file_info> <file_info> <name>hcckernel.cl.7.05</name> <executable/> </file_info> <file_info> <name>wcg_hcc1_img_7.05_windows_intelx86</name> <executable/> </file_info> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <plan_class>ati_hcc1</plan_class> <avg_ncpus>1.0</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>ATI</type> <count>.5</count> </coproc> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name> <main_program/> </file_ref> <file_ref> <file_name>hcckernel.cl.7.05</file_name> <open_name>hcckernel.cl</open_name> </file_ref> </app_version> <app_version> <app_name>hcc1</app_name> <version_num>705</version_num> <platform>windows_intelx86</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>3231932486.733310</flops> <api_version>6.13.0</api_version> <file_ref> <file_name>wcg_hcc1_img_7.05_windows_intelx86</file_name> <main_program/> </file_ref> </app_version> </app_info> Let me know how it goes. nanoprobe, once again thanks for this and your easy to follow instructions. I intended to test this today once all apps in my buffer had been processed, but when I looked, I saw that there were over 1000 ATI units waiting, so I decided to do a test of my own. Since that machine was already doing GPU and CPU tasks, I figured there was no need to stop, remove app_info.xml, restart, wait for buffer to fill, stop and then apply the new app_info.xml. So what I did was simply stop,swap old app_info.xml with the new one and restart. After that, all I needed to do was restart the WUs. Obviously, I will have to follow your instructions on the other machine because it is only running GPU at the moment. I'll give feedback on how that goes soon. Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges: |
Second machine: Introducing CPU tasks to a machine doing GPU tasks exclusively.
----------------------------------------To do this, I followed nanoprobe's directions to the letter. The only 'panic' moment was when restarting with no app_info.xml in the projects folder, it seemed to take an age to start to download CPU tasks. Rather than detach and reattach, I did a project update and was soon downloading CPU tasks. Once they had downloaded, it was simple to suspend, insert the new app_info.xml and restart BM. Both machines appear to be running as expected, so I am now going to start on a third machine (using nanoprob's app_info.xml) to which I will introduce the 5770 which I removed from one of the other two a few days ago. Thanks again, nanoprobe Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
My pleasure.
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
Country Bumkin
Cruncher Australia Joined: May 14, 2008 Post Count: 14 Status: Offline Project Badges: |
I am trying to make an app_info file for use on a Linux 64 + Nvidia system. Attempts to convert windows app_info files have produced inscrutable missing file errors. Could people post some working Linux examples for use as templates.
----------------------------------------What is the recommeded procedure to install the app_info file ?
Regards C Bumkin
----------------------------------------[Edit 1 times, last edit by Country Bumkin at Dec 12, 2012 3:31:29 AM] |
||
|
|