| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: App_Config and beta's Questions |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: 
|
I built a fresh win 7 install and put gpu only on it and then an app_info to maximise output.
----------------------------------------I upgraded to boinc 7.0.42 and changed to app_config. I read about the differences between the two app methods and then set up to run some cpu projects. This was the first time I ran into a small issue in that the rig had not run these before so I had to stop using app_config for a while in order to download the correct files. and then when I went back to app_config all was well except for dddt and beta. My questions: How do I get those files on my computer in order that I can run them (especially beta's) when they are available? Will there be an issue when the beta is of a new type? Gpu prioritises over CPU and beta's prioritise themselves too but will beta's prioritise over GPU? These questions posed could perhaps be summarised by asking: When running app_config can I still find a way of continuing to complete beta work on cpu especially if normal running devotes all cores to the GPU?  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
During the recent C4CW BETA I just checked Do work on CPU and checked an intermitent project.DDDT2 which was not running so I got BETAs.
7.042 + config on GPU only machine. |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
During the recent C4CW BETA I just checked Do work on CPU and checked an intermitent project.DDDT2 which was not running so I got BETAs. 7.042 + config on GPU only machine. I have a separate profile with the same settings. I just switch profiles on my GPU only machines when I see that betas are available.
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 |
Changing 5,6,7,8+ machines to a different profile is a lot of clicks.Changing the profile is click two boxes-save.
|
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
I built a fresh win 7 install and put gpu only on it and then an app_info to maximise output. I upgraded to boinc 7.0.42 and changed to app_config. I read about the differences between the two app methods and then set up to run some cpu projects. This was the first time I ran into a small issue in that the rig had not run these before so I had to stop using app_config for a while in order to download the correct files. and then when I went back to app_config all was well except for dddt and beta. My questions: How do I get those files on my computer in order that I can run them (especially beta's) when they are available? Will there be an issue when the beta is of a new type? You only need to add an app to your app_config.xml if you'll need to change it's default behaviour, meaning example to run multiple GPU-tasks on a single GPU, or to max run N CEP2 at once. DDDT2 and beta will therefore be treaded just like if you've not got an app_config.xml at all. Gpu prioritises over CPU and beta's prioritise themselves too but will beta's prioritise over GPU? CPU, Amd and Nvidia each uses separate queues, so a Beta-CPU-task will never be prioritised over a non-beta-GPU-task. A Beta-Amd-task can on the other hand be prioritised over a non-beta--Amd-task. These questions posed could perhaps be summarised by asking: When running app_config can I still find a way of continuing to complete beta work on cpu especially if normal running devotes all cores to the GPU? If GPU-tasks uses all your cores to run, it will continue to do this as long as you've got enough GPU-tasks on client, regardless of any CPU-work missing their deadline. To run some beta-work on CPU this means you'll need to pause GPU-crunching until the beta-work has finished.  "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:
|
Changing 5,6,7,8+ machines to a different profile is a lot of clicks.Changing the profile is click two boxes-save. That's assuming you have all your machines set to the same profile before making the changes. I don't so my way works best for me. 
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 |
............. To run some beta-work on CPU this means you'll need to pause GPU-crunching until the beta-work has finished. I had to do this to free up a core for each BETA.They would have gone No Reply otherwise. |
||
|
|
|