Message boards :
New Runs for MilkyWay@home Nbody Simulations (07/29/2020)
Posted 8 Sep 2020 by Kristoffer
Actually the correct method of defining mt app is provided in the BOINC configuration document.
Thanks a lot! Looks like it solved my issue as well!
By default the milkyway_nbody process was single instance, distributed over all my threads, taking several days to finish. The CPU utilisation was almost nada, ie idling around 1% overall.
The latter variant of the xml-file seems to work well in my case. After Jim's advice, I restricted it to only a single thread per process, and increased the maximum number of parallel processes accordingly.
After saving the app_config.xml in the projects app-data folder, I suspended the milkyway project, waited a minute or so, then resumed. The ongoing process then resumed without any visible change, and finished in about 25 mins what it had spent several days doing already. Full CPU utilisation on all cores/threads.
So, great! However, weird that this isn't solved on the server side as others have pointed out. It's a real time waste for the other projects when the milkyway instances are run so inefficiently..
For reference, here's my C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\app_config.xml
<app_config> <app> <name>milkyway_nbody</name> <max_concurrent>8</max_concurrent> </app> <app_version> <app_name>milkyway_nbody</app_name> <plan_class>mt</plan_class> <cmdline>--nthreads 1</cmdline> </app_version> </app_config>
©2021 Astroinformatics Group