Message boards :
ATLAS application :
No App config task limts
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Sep 08 Posts: 801 Credit: 649,858,067 RAC: 240,453 |
Hi, I have the setting on the web to set the max number of cores to two, with 24 Tasks max, however this doesn't work well. BOINC doesn't respect or know the number of cores in the WU's so it tries to run 24 2 core WU on a 24 core machine so the performance so so. Can this be addressed? |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,464,258 RAC: 5,837 |
|
Send message Joined: 27 Sep 08 Posts: 801 Credit: 649,858,067 RAC: 240,453 |
Yes, it has the (2) after the task, it's strange |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,464,258 RAC: 5,837 |
|
Send message Joined: 27 Sep 08 Posts: 801 Credit: 649,858,067 RAC: 240,453 |
I'll give it ago |
Send message Joined: 27 Sep 08 Posts: 801 Credit: 649,858,067 RAC: 240,453 |
OK, I tried it and it works if there is all atlas, but in a mixed scenario it doesn't work. The setting are 24 WU's if you have 10 Atlas and 14 others, this is 34 cores used on a 24core machine. I guess it's the same as the other memory problems, BOINC doesn't actually know what the VM is doing so it doesn't allocate resources correctly. |
Send message Joined: 17 Sep 04 Posts: 99 Credit: 30,638,818 RAC: 1,711 |
[quote] How do I combine this (or do I?) with the command to limit ATLAS to 2-cores per work unit? Thanks! Regards, Bob P. |
Send message Joined: 18 Dec 15 Posts: 1687 Credit: 102,954,212 RAC: 125,722 |
How do I combine this (or do I?) with the command to limit ATLAS to 2-cores per work unit?the number of cores per task you set in your web-settings ("preferences") |
Send message Joined: 15 Jun 08 Posts: 2401 Credit: 225,366,105 RAC: 123,240 |
... How do I combine this (or do I?) with the command to limit ATLAS to 2-cores per work unit? See the following example that combines ATLAS 2core and CMS singlecore: <app_config> <app> <name>ATLAS</name> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>ATLAS</app_name> <plan_class>vbox64_mt_mcore_atlas</plan_class> <avg_ncpus>2</avg_ncpus> <cmdline>--nthreads 2 --memory_size_mb 5000</cmdline> </app_version> <app> <name>CMS</name> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>CMS</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>1</avg_ncpus> <cmdline>--nthreads 1</cmdline> </app_version> <project_max_concurrent>2</project_max_concurrent> </app_config> A complete explanation can be found in the BOINC documentation: http://boinc.berkeley.edu/wiki/client_configuration#Application_configuration |
Send message Joined: 17 Sep 04 Posts: 99 Credit: 30,638,818 RAC: 1,711 |
Thanks! The problem I have is that 11 instances of ATLAS 2-core download, but then only 7 of them run. With my allocating 22 cores to LHC, the 4 ATLAS 2-cores that are there but not running prevent other LHC work units from running. So i an stuck with just 14 of my 22 cores running. Regards, Bob P. |
©2024 CERN