Message boards :
Number crunching :
ATLAS is now MT?
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Sep 04 Posts: 108 Credit: 8,397,596 RAC: 1,313 ![]() ![]() ![]() |
Got home this evening to find only two apps running on my HT hex core system then finally noticed that ATLAS was using 11 of them!! For a process that runs in Windows,I can use something like this <app_config> <project_max_concurrent>2</project_max_concurrent> <app_version> <app_name>ATLAS</app_name> <cmdline>nthreads 2</cmdline> <avg_ncpus>2</avg_ncpus> <plan_class>mt</plan_class> </app_version> </app_config> To limit the number of "CPUs" used but this gives me an error of Entry in app_config.xml for app 'ATLAS', plan class 'mt' doesn't match any app versions Anybody have any suggestions? Thanks in advance for any assistance ![]() ![]() |
Send message Joined: 14 Jan 10 Posts: 1446 Credit: 9,710,991 RAC: 196 ![]() ![]() |
Anybody have any suggestions? Take what you need: <app_config> <project_max_concurrent>6</project_max_concurrent> <app> <name>ALICE</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app> <name>ATLAS</name> <max_concurrent>2</max_concurrent> <fraction_done_exact/> </app> <app> <name>Benchmark</name> <max_concurrent>4</max_concurrent> <fraction_done_exact/> </app> <app> <name>CMS</name> <max_concurrent>4</max_concurrent> <fraction_done_exact/> </app> <app> <name>LHCb</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app> <name>sixtrack</name> <max_concurrent>4</max_concurrent> <fraction_done_exact/> </app> <app> <name>Theory</name> <max_concurrent>4</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>ALICE</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>1.000000</avg_ncpus> <cmdline>--nthreads 1.000000</cmdline> <cmdline>--memory_size_mb 630</cmdline> </app_version> <app_version> <app_name>ATLAS</app_name> <plan_class>vbox64_mt_mcore_atlas</plan_class> <avg_ncpus>2.000000</avg_ncpus> <cmdline>--memory_size_mb 5000</cmdline> </app_version> <app_version> <app_name>Benchmark</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>1.000000</avg_ncpus> <cmdline>--nthreads 1.000000</cmdline> <cmdline>--memory_size_mb 1408</cmdline> </app_version> <app_version> <app_name>CMS</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>1.000000</avg_ncpus> <cmdline>--memory_size_mb 1896</cmdline> </app_version> <app_version> <app_name>Theory</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>1.000000</avg_ncpus> <cmdline>--memory_size_mb 630</cmdline> </app_version> </app_config> |
Send message Joined: 27 Sep 08 Posts: 863 Credit: 714,182,683 RAC: 196,228 ![]() ![]() ![]() |
I'd recommend that you set the max # of CPU's to 3, then the ATLAS tasks get about the right amount of memory reported to BOINC to allow the total memory consumption to not over load your computer too. I have this: <app_config> <app> <name>ATLAS</name> <max_concurrent>12</max_concurrent> </app> <app_version> <app_name>ATLAS</app_name> <plan_class>vbox64_mt_mcore_atlas</plan_class> <avg_ncpus>2.0</avg_ncpus> <cmdline>--memory_size_mb 4900</cmdline> </app_version> </app_config> <!--Set WebSettings to 3 Cores, 5GB--> In this case max concurrent = 64GB/5GB = 12.8 rounded down = 12 |
Send message Joined: 27 Sep 04 Posts: 108 Credit: 8,397,596 RAC: 1,313 ![]() ![]() ![]() |
Thanks,both of you I've updated my app_config, but am now caught in the "not highest prioority" blackhole we'll see what happens |
©2025 CERN