Sticky app_config.xml parameters

Questions and Answers : Windows : Sticky app_config.xml parameters
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1974542 - Posted: 10 Jan 2019, 18:41:36 UTC

Over the years I have had cases where I wanted to disable the CPU to GPU ratio in the app_config.xml file.

So I would rename the file to something like app_config_stop.xml and then stop, pause restart the BOINC Manager. On Linux, it always goes to the "default" CPU to GPU ratio.

On Windows, it doesn't always work. Besides just putting in my best guess for the default CPU to GPU ratio which file should I delete to get rid of the "memory"?

Tom
A proud member of the OFA (Old Farts Association).
ID: 1974542 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 1974707 - Posted: 11 Jan 2019, 8:00:16 UTC - in response to Message 1974542.  

Default gpu_usage is 10X peak CPU speed (gpu_usage.usage * 10 * host_info.p_fpops)
Default cpu_usage is 1 per task.

That's then later changed by the science application that comes with its own values. These values are stored in client_state.xml, however it is possible that the defaults are overwritten by the self-set. Another place that can hold these values is in the app_info.xml file. I cannot search the wikis at the moment because their databases are down.
ID: 1974707 · Report as offensive

Questions and Answers : Windows : Sticky app_config.xml parameters


 
©2022 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.