If you want to avoid these tasks in the future, add this line to the "options" section of your cc_config.xml file and then restart the boinc client.
<dont_use_vbox>1</dont_use_vbox>
On my 3700X with 32 GB RAM, I've been making adjustments to an app_config.xml and have completed 2 resend tasks successfully.
Normally the creates a VM for each task using one thread and reserves 6.14 GB RAM. I'm not sure how much disk space is used per thread but I retrieved this info from one completed task:
Peak working set size 1,564.48 MB
Peak swap size 6,164.10 MB
Peak disk usage 12,930.47 MB
Code: Select all
<app_config>
<app_version>
<app_name>rosetta_python_projects</app_name>
<version_num>102</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<avg_ncpus>2.000000</avg_ncpus>
<plan_class>vbox64</plan_class>
<api_version>7.7.0</api_version>
<max_concurrent>2</max_concurrent>
<dont_throttle/>
</app_version>
<app_version>
<app_name>rosetta</app_name>
<version_num>420</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<avg_ncpus>1.000000</avg_ncpus>
<api_version>7.9.0</api_version>
</app_version>
<project_max_concurrent>14</project_max_concurrent>
</app_config>
Would a VM task benefit by adding an extra thread to each VM to handle VM "overhead" processes? It's not a multi threaded app (vbox_mt) like the Cosmo camb_boinc2docker application.