Advanced search

Message boards : Technical Support : camb_boinc2docker 2.04 not respecting ncpu limit

Author Message
Variable
Send message
Joined: 21 Oct 17
Posts: 7
Credit: 441,211
RAC: 16,417
Message 21564 - Posted: 27 Oct 2017, 0:24:22 UTC

As the title says, I'm trying to limit the number of threads cosmology will use on my 4790 box but it is not respecting the limit I put in the app_config file:

<app_config>

<project_max_concurrent>1</project_max_concurrent>

<app_version>
<app_name>camb_boinc2docker</app_name>
<plan_class>vbox64_mt</plan_class>
<avg_ncpus>3</avg_ncpus>
</app_version>

</app_config>

BOINC is recognizing the config file and I can see the task says (3 CPUs), yet as soon as I turn it on it slams CPU usage to 100%, with no other competing tasks running. This renders the machine unusable and actually locked it up earlier today. Any ideas to fix this?

Variable
Send message
Joined: 21 Oct 17
Posts: 7
Credit: 441,211
RAC: 16,417
Message 21565 - Posted: 27 Oct 2017, 1:25:22 UTC

Actually I think I Just figured it out. It was running tasks that had been downloaded right after attaching this machine to the project, and they were all calling 8 threads (the max this box has), I could see it in the VBox manager. I aborted all those, and now the new tasks that just downloaded are only using the ncpus that I'm specifiying. Problem seems to be solved.

Message boards : Technical Support : camb_boinc2docker 2.04 not respecting ncpu limit