feat: boinc data for the docker container

This commit is contained in:
Michele Cereda
2023-06-03 20:17:15 +02:00
parent 02827f15f0
commit 85cfdda657
2 changed files with 106 additions and 0 deletions

View File

@@ -0,0 +1,42 @@
<!--
${BOINC_DATA_DIR}/cc_config.xml
Configuration file for the BOINC core client.
See https://boinc.berkeley.edu/wiki/Client_configuration#Client_configuration
for a complete list of all the available options.
-->
<cc_config>
<options>
<!-- Abort jobs and update projects when the client exits. -->
<abort_jobs_on_exit>1</abort_jobs_on_exit>
<!--
Report jobs to the project server as soon as they are finished.
Satisfies the inbuilt 60 second delay from the completion of the
result's upload.
-->
<report_results_immediately>1</report_results_immediately>
<!-- Don't accept jobs for VirtualBox. -->
<dont_use_vbox>1</dont_use_vbox>
<!-- Exempt non-CPU-intensive tasks from most cases of suspension. -->
<dont_suspend_nci>1</dont_suspend_nci>
<!--
Allow GUI RPCs from *any* remote host.
See https://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely.
-->
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
</options>
<log_flags>
<!-- On by default. -->
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
</log_flags>
</cc_config>

View File

@@ -0,0 +1,64 @@
<!--
${BOINC_DATA_DIR}/global_prefs_override.xml
Configuration file for the BOINC core client that can be used to override global
preferences locally.
See http://boinc.berkeley.edu/trac/wiki/PrefsOverride,
https://boinc.berkeley.edu/trac/wiki/PrefsImpl and
https://boinc.berkeley.edu/wiki/Global_prefs_override.xml for a complete list
of all preferences which can be overridden.
-->
<global_preferences>
<!-- Use the BoincStats account manager. -->
<source_project>http://bam.boincstats.com/</source_project>
<!-- Run always. -->
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<!-- Always be active on the network. -->
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<!--
Suspend computation if the user is active.
Wait 3 minutes before starting again.
-->
<run_if_user_active>0</run_if_user_active>
<run_gpu_if_user_active>0</run_gpu_if_user_active>
<idle_time_to_run>3</idle_time_to_run>
<!--
Limit resource usage.
The stricter ones have precedence.
-->
<max_cpus>1024</max_cpus>
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<suspend_cpu_usage>75</suspend_cpu_usage>
<ram_max_used_idle_pct>100</ram_max_used_idle_pct>
<ram_max_used_busy_pct>90</ram_max_used_busy_pct>
<vm_max_used_pct>100</vm_max_used_pct>
<disk_max_used_gb>1024</disk_max_used_gb>
<disk_max_used_pct>90</disk_max_used_pct>
<disk_min_free_gb>1</disk_min_free_gb>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<!--
Avoid buffering tasks.
This is an ephemeral system after all.
-->
<work_buf_min_days>0</work_buf_min_days>
<work_buf_additional_days>0</work_buf_additional_days>
<!--
Save data and reschedule every often.
I do not expect a container to run too long.
-->
<cpu_scheduling_period_minutes>10</cpu_scheduling_period_minutes>
<disk_interval>60</disk_interval>
</global_preferences>