Message boards :
Theory Application :
Theory and app_config ?
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,464,258 RAC: 5,837 |
To fix the problem with my host, I wanted to establish an app_config.xml that tells Theory to use only 1 task. But so far I'm not succesfull. 1) Does Theory work with app_config ? 2) Can someone provide me with the content of a working app_config for Theory to use only 1 Core ? I tried this one: <app_config> <project_max_concurrent>1</project_max_concurrent> <app> <name>ATLAS</name> <max_concurrent>1</max_concurrent> </app> <app> <name>Theory</name> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>ATLAS</app_name> <version_num>100</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <plan_class>vbox64_mt_mcore_atlas</plan_class> <api_version>7.7.0</api_version> <cmdline>--memory_size_mb 5000</cmdline> <dont_throttle/> <is_wrapper/> <needs_network/> </app_version> <app_version> <app_name>Theory</app_name> <version_num>26320</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <plan_class>vbox64</plan_class> <api_version>7.7.0</api_version> <dont_throttle/> <is_wrapper/> <needs_network/> </app_version> <app_version> <app_name>Theory</app_name> <version_num>26370</version_num> <platform>windows_x86_64</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <plan_class>vbox64</plan_class> <api_version>7.7.0</api_version> <cmdline>--memory_size_mb 930</cmdline> <dont_throttle/> <is_wrapper/> <needs_network/> </app_version> </app_config> Supporting BOINC, a great concept ! |
Send message Joined: 21 Jun 10 Posts: 40 Credit: 10,713,363 RAC: 4,865 |
Hi Yeti, Try the following app_config.xml <app_config> <app> <name>Theory</name> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>Theory</app_name> <avg_ncpus>1.0</avg_ncpus> <plan_class>vbox64_mt_mcore</plan_class> <cmdline>--nthreads 1</cmdline> </app_version> </app_config> I just put this together and it appears to be working running theory on one thread. The two main differences are the plan_class and the addition of a cmdline for --nthreads. Also, in your app_config, there are several parameters that I do not find in the BOINC documentation for client configuration http://boinc.berkeley.edu/wiki/client_configuration. I do not know how the undocumented parameters in your app_config affect the client configuration, my suggestion is to use the minimum parameters until you find something that works then add parameters. Also, just in case you didn't know, when you add parameters to an app_config, you can activate the new parameters by clicking on "Options", "Read Config Files" in the BOINC Manager. If you need to remove parameters, it is best to shut down BOINC and start it back up with the new parameters in place. Hope that helps, let us know how it turns out. |
Send message Joined: 15 Jun 08 Posts: 2401 Credit: 225,326,375 RAC: 123,023 |
Theory uses a new plan_class since it changed to multicore. This snippet would configure the default 1-core setup: <app_version> <app_name>Theory</app_name> <plan_class>vbox64_mt_mcore</plan_class> <avg_ncpus>1.000000</avg_ncpus> <cmdline>--memory_size_mb 730</cmdline> </app_version> It's highly recommended to use only 1 section for each app. Your app_config.xml contains lots of garbage that will be ignored by the BOINC client. You may check the BOINC documentation to see which parameters are allowed and how they have to be ordered. http://boinc.berkeley.edu/wiki/client_configuration#Application_configuration |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,464,258 RAC: 5,837 |
|
Send message Joined: 21 Jun 10 Posts: 40 Credit: 10,713,363 RAC: 4,865 |
You are welcome, glad you got it working. One other clue that you might find useful in the future, it there is any doubt about which names to use in the app_config.xml, you can find many of the names for the current version in the client_state_prev.xml file located in the BOINC data folder. Good luck with your crunching. |
©2024 CERN