#BOINC CONFIG FILE LOCATION HOW TO#
I do now understand how to set the total number of tasks (#gpus X (number of tasks per card based on (1/x tasks = decimal number to set gpu_usage). I have been tinkering with the cc_config.xml file and the app_config.xml files. I am getting the app_info.xml file and the app_config.xml file confused. But for fine tuning the scheduling process, it's best to use the app_config.xml file. Many of the things you can do in the app_config.xml file, you can do in the app_info.xml file. You can use an app_info.xml file at all times, with or without an additional app_config.xml file. This way you can use apps that are optimized specifically for your CPU/GPU, or that you compiled yourself. The application information file (app_info.xml) is used by anonymous platform applications, and is used so the user can dictate to BOINC what application it should run instead of the default science application provided by the project. This file can be used with the default project provided science applications, and the third party science applications used through the anonymous platform module. With this file you can configure how many tasks BOINC should schedule to run on an appointed application and GPU. is the application configuration file, its name shortened to app_config.xml So could you please elaborate? As far as I know, I didn't refer to gpu_type anywhere.Īs I have written elsewhere in answer to you as well, since you continue to say app_info.xml where you mean app_config.xml: Perhaps that the question setting makes sense for you, but it doesn't for me. Although both, since they work on a per-project basis, run from the project directory.įor "gpu type" I think you are referring to cc_config.xml and in app_config.xml is the "coproc"? Please do not confuse the one with the other. It is used by anonymous platform applications - which are non-default by project delivered, non-downloaded automatically by BOINC applications - and is described in. It may be gone by day-break tomorrow.Īpp_info.xml is a whole different kettle of fish. So even when I today put in the information into that Wiki, I cannot guarantee that it will stay there. One has to keep in mind that the main developer (and boss, owner etc.) of BOINC (not Bionic, certainly not Bionnic unless you know what that acronym stands for?) goes through the User Wiki and weeds out what he finds superfluous and useless information on a regular basis. How does gpu_usage interact with cpu_usage? Why does it cause (usually) 2 tasks on each of two gpus? To do this, create a file app_config.xml in the project's directory, e.g. It is available with 7.0.40+ client versions. This mechanism allows you to specify scheduling parameters for specific applications or app versions. The Application configuration section starts with: And it doesn't answer the question of:Īpp_info.xml (you mean app_config.xml - Jord) -> in the Seti at home project directory I don't know the specifics of it but I know if you don't use it and have different GPUs of non-similiar speed or class, Bonic will only use the higher rated class. What this is telling the program is to use all available graphic cards.
It would be easy to say that these portions of the cores are reserved but in truth they are "floating" meaning that they rotate between all the cores. If the number was 0.33 then it's 3 work units per Core. Again 0.5 is 1/2 so use each core supports 2 work units.
Now the CPU usage tells the program how much of each core to use. If the number was 0.33 then it would use 1/3 of the GPU for each work unit, so 0.33 means 3 work units per GPU. So 1/2 of a GPU then means 2 work units per GPU. GPU 0.5 tells the program to use 1/2 of a gpu for each work unit.
#BOINC CONFIG FILE LOCATION FREE#
The GNU Free Documentation License, Version 1.The above tells program what ratio of GPU to CPU. Permission is granted to copy, distribute and/or modify this document under the terms of Tell the client to retry deferred network communication.Ĭopyright © 2007-2008 University of California. Tell the client to reread the configuration file ( cc_config.xml).įetch configuration of project located at URL. Tell the client to read the global_prefs_override.xml file and incorporate any set_proxy_settings http_server_name http_server_port http_user_name http_user_passwd socks_server_name socks_server_port socks5_user_name socks5_user_passwd noproxy_hosts Like -set_run_mode but applies to GPU processing only. Provided by: boinc-client_7.9.3+dfsg-5_amd64īoinccmd - The command line interface to the BOINC client.
0 kommentar(er)
