| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Outsmart Ebola Together
Thread: [Solved] WU usage. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have a little problem you might be able to help me with. My LINUX PC is running two GPUs. I have WCG Outsmart Ebola Together and Collatz Conjecture running. Collatz Conjecture is set for 0.25C+0.25NV and is running fine with 6 WCG WUs and 8 Collatz Conjecture GPU WUs.
----------------------------------------The problem is, with one additional WCG "Ready to Start" WU downloaded, one of the GPUs is put to "Waiting to Run" (that is four WUs), and the 7th WCG WU is started running in place of the four GPU WUs. My work around is to Suspend the "Ready to Start" WCG WUs and one of the "Running" WCG WUs and that opens the processor space for the 4 Collatz WUs to resume running. Is that crazy enough for you? It would be nice, if you knew what was happening and had a solution so I didn't have to shuffle the WUs around like this. This is as clear as I can put the problem. If additional info is needed just ask, but please be specific as to how I collect the required data. Thank [Edit 1 times, last edit by Former Member at Jul 12, 2015 1:04:49 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Have you already been using the app_config.xml functionality? With that you can control how many OET1 can run concurrently.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Rob...
<app_config> <app> <name>solo_collatz</name> <max_concurrent>16</max_concurrent> <gpu_versions> <gpu_usage>0.25</gpu_usage> <cpu_usage>0.25</cpu_usage> </gpu_versions> </app> <app> <name>mini_collatz</name> <max_concurrent>16</max_concurrent> <gpu_versions> <gpu_usage>0.25</gpu_usage> <cpu_usage>0.25</cpu_usage> </gpu_versions> </app> </app_config> |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, now that one is supposed to be in the Collatz project folder. Make another one for the WCG folder with,,,
----------------------------------------<app_config> <app> <name>oet1</name> <max_concurrent>6</max_concurrent> <fraction_done_exact/> </app> </app_config> or however many more or less OET1 you wish to allow. [Edit 1 times, last edit by Former Member at Jul 12, 2015 12:08:22 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, Rob...I guess you think you're real smart. Well, you are.
----------------------------------------Fixed it on the first try. I didn't even realize the WCG folder needed an app_config. Thanks much, Rob. [Edit 1 times, last edit by Former Member at Jul 12, 2015 1:03:59 AM] |
||
|
|
Highlander_6596
Cruncher Joined: May 6, 2014 Post Count: 10 Status: Offline Project Badges: 
|
What is the app_config name for FightAIDS@Home?
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
fahv for the AD Vina version that's running now
----------------------------------------faah for the old Autodock app. (Short) names can always be found in the client_state.xml and usually [not always] are also part of the task names at front, but it's got to be specified lower case! Edit: Users of the BOINCTasks BOINC Manager (BM) substitute have the benefit that the actual short names are listed in the Tasks view [Don't see it in the BM or the tasks properties of that manager. [Edit 2 times, last edit by Former Member at Jul 26, 2015 11:27:47 AM] |
||
|
|
|