Welcome to MilkyWay@home

How to access app_info.xml?

Message boards : Number crunching : How to access app_info.xml?
Message board moderation

To post messages, you must log in.

AuthorMessage
kurt

Send message
Joined: 17 Nov 10
Posts: 12
Credit: 482,185,206
RAC: 2,114
Message 52290 - Posted: 7 Jan 2012, 20:26:28 UTC

How do I go about accessing the app_info.xml?I'm running win7 64bit w/a 6870+a 4870.I would like to use the 4870 on MW and the 6870 on seti or collatz.Is it possible?Thanks,Kurt
ID: 52290 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,594,787
RAC: 30,307
Message 52306 - Posted: 8 Jan 2012, 12:21:17 UTC - in response to Message 52290.  

How do I go about accessing the app_info.xml?I'm running win7 64bit w/a 6870+a 4870.I would like to use the 4870 on MW and the 6870 on seti or collatz.Is it possible?Thanks,Kurt


The app_info file is not something that is included in Boinc, it is a handmade file, or better yet a copy of someone elses, that is modified to fit your parameters. And yes it is possible but it will not be straightforward! In the app_info file you will just exclude 1 gpu, you will end up needing two of them as you will need to exclude 1 gpu in each. You will also need to have two TOTALLY SEPARATE installations of Boinc in TOTALLY DIFFERENT locations! Then one app_info file goes into each location letting a gpu crunch for it. It would be MUCH easier if you just used a second pc and put one gpu in each.
ID: 52306 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Semtex

Send message
Joined: 10 Dec 11
Posts: 3
Credit: 10,302,843
RAC: 0
Message 52307 - Posted: 8 Jan 2012, 13:07:31 UTC - in response to Message 52290.  

You can try to disable gpu for specified project.
This should be done in cc_config.xml

...
<exclude_gpu>

Don't use the given GPU for the given project. If <device_num> is not specified, exclude all GPUs of the given type. <type> is required if your computer has more than one type of GPU; otherwise it can be omitted. <app> specifies the short name of an application (i.e. the <name> element within the <app> element in client_state.xml). If specified, only tasks for that app are excluded. You may include multiple <exclude_gpu> elements. List-add.pngNew in 6.13

<exclude_gpu>
<url>project_URL</url>
[<device_num>N</device_num>]
[<type>nvidia|ati</type>]
[<app>appname</app>]
</exclude_gpu>
...

More info: http://boinc.berkeley.edu/wiki/Client_configuration
ID: 52307 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,594,787
RAC: 30,307
Message 52310 - Posted: 8 Jan 2012, 14:36:06 UTC - in response to Message 52307.  

You can try to disable gpu for specified project.
This should be done in cc_config.xml

...
<exclude_gpu>

Don't use the given GPU for the given project. If <device_num> is not specified, exclude all GPUs of the given type. <type> is required if your computer has more than one type of GPU; otherwise it can be omitted. <app> specifies the short name of an application (i.e. the <name> element within the <app> element in client_state.xml). If specified, only tasks for that app are excluded. You may include multiple <exclude_gpu> elements. List-add.pngNew in 6.13

<exclude_gpu>
<url>project_URL</url>
[<device_num>N</device_num>]
[<type>nvidia|ati</type>]
[<app>appname</app>]
</exclude_gpu>
...

More info: http://boinc.berkeley.edu/wiki/Client_configuration


SORRY I always seem to get the cc_config and app_info files confused as to which is which and can do what!
ID: 52310 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0
Message 52324 - Posted: 8 Jan 2012, 21:22:44 UTC - in response to Message 52306.  

In the app_info file you will just exclude 1 gpu, you will end up needing two of them as you will need to exclude 1 gpu in each. You will also need to have two TOTALLY SEPARATE installations of Boinc in TOTALLY DIFFERENT locations! Then one app_info file goes into each location letting a gpu crunch for it. It would be MUCH easier if you just used a second pc and put one gpu in each.
I don't think that this is true. app_info.xml is per project and they should be able to coexist.
ID: 52324 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,594,787
RAC: 30,307
Message 52338 - Posted: 9 Jan 2012, 12:52:23 UTC - in response to Message 52324.  

In the app_info file you will just exclude 1 gpu, you will end up needing two of them as you will need to exclude 1 gpu in each. You will also need to have two TOTALLY SEPARATE installations of Boinc in TOTALLY DIFFERENT locations! Then one app_info file goes into each location letting a gpu crunch for it. It would be MUCH easier if you just used a second pc and put one gpu in each.


I don't think that this is true. app_info.xml is per project and they should be able to coexist.


I don't know, but I SHOULD have been saying cc_config.xml not app_info.xml I get confused on which does what and then confuse myself even worse! The point was to get two different installations of Boinc, then each can run its own project. What I think you are saying is it might work with a single installation if each Project had a gpu exclusion line in it, correct.
ID: 52338 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
wizzo

Send message
Joined: 30 Mar 11
Posts: 3
Credit: 33,257,271
RAC: 0
Message 52357 - Posted: 10 Jan 2012, 23:23:49 UTC

My CC_CONFIG
I run milkyway, collatz, albert, and poem.
Poem excludes gpus 0 & 2, and gets to use the rest (1 & 3), milkyway, collatz, and albert exclude gpu's 1 & 3, and share the rest (0 & 2).

*****************************
<cc_config>
<options>
<exclude_gpu><url>http://milkyway.cs.rpi.edu/milkyway/</url><device_num>3</device_num></exclude_gpu>
<exclude_gpu><url>http://boinc.thesonntags.com/collatz/</url><device_num>3</device_num></exclude_gpu>
<exclude_gpu><url>http://albert.phys.uwm.edu/</url><device_num>3</device_num></exclude_gpu>
<exclude_gpu><url>http://albert.phys.uwm.edu/</url><device_num>1</device_num></exclude_gpu>
<exclude_gpu><url>http://milkyway.cs.rpi.edu/milkyway/</url><device_num>1</device_num></exclude_gpu>
<exclude_gpu><url>http://boinc.thesonntags.com/collatz/</url><device_num>1</device_num></exclude_gpu>

<exclude_gpu><url>http://boinc.fzk.de/poem/</url><device_num>2</device_num></exclude_gpu>
<exclude_gpu><url>http://boinc.fzk.de/poem/</url><device_num>0</device_num></exclude_gpu>
</options>
</cc_config>
****************************************
ID: 52357 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : How to access app_info.xml?

©2024 Astroinformatics Group