How to change checkpointing and suspend boinc network via config file?

[Endgame124]

Quick pair of questions.

I would like to identify how frequently a project takes checkpoints, and then change it. I see checkpoints listed in a rosetta file (sched_request_boinc.bakerlab.org_rosetta.xml) at 120s, but I'm not sure if there is a global setting, or if this is even configurable for all projects.

My next question is for suspending boinc network usage. Where do I find the configuration in the config files (cc_config.xml?) , and can I set it for multiple time periods? For example, can I allow network traffic 6am-7am, noon-1pm, 6pm-7pm, and midnight-1am?

Thanks in advance!

 

[Skillz]

Quick pair of questions.

I would like to identify how frequently a project takes checkpoints, and then change it. I see checkpoints listed in a rosetta file (sched_request_boinc.bakerlab.org_rosetta.xml) at 120s, but I'm not sure if there is a global setting, or if this is even configurable for all projects.

Not 100% sure on this, but it's usually controlled by the project itself.

My next question is for suspending boinc network usage. Where do I find the configuration in the config files (cc_config.xml?) , and can I set it for multiple time periods? For example, can I allow network traffic 6am-7am, noon-1pm, 6pm-7pm, and midnight-1am?

Thanks in advance!

That's located in the global_prefs_override.xml file. Here is an example. You can use the GUI to do this as well. (I used the GUI to fill in these values)

<global_preferences>
   <run_on_batteries>0</run_on_batteries>
   <run_if_user_active>1</run_if_user_active>
   <run_gpu_if_user_active>1</run_gpu_if_user_active>
   <suspend_cpu_usage>0.000000</suspend_cpu_usage>
   <start_hour>0.000000</start_hour>
   <end_hour>24.000000</end_hour>
   <net_start_hour>0.000000</net_start_hour>
   <net_end_hour>24.000000</net_end_hour>
   <leave_apps_in_memory>1</leave_apps_in_memory>
   <confirm_before_connecting>1</confirm_before_connecting>
   <hangup_if_dialed>1</hangup_if_dialed>
   <dont_verify_images>1</dont_verify_images>
   <work_buf_min_days>0.100000</work_buf_min_days>
   <work_buf_additional_days>0.100000</work_buf_additional_days>
   <max_ncpus_pct>100.000000</max_ncpus_pct>
   <cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
   <disk_interval>60.000000</disk_interval>
   <disk_max_used_gb>0.000000</disk_max_used_gb>
   <disk_max_used_pct>98.000000</disk_max_used_pct>
   <disk_min_free_gb>0.000000</disk_min_free_gb>
   <vm_max_used_pct>75.000000</vm_max_used_pct>
   <ram_max_used_busy_pct>95.000000</ram_max_used_busy_pct>
   <ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
   <max_bytes_sec_up>0.000000</max_bytes_sec_up>
   <max_bytes_sec_down>0.000000</max_bytes_sec_down>
   <cpu_usage_limit>100.000000</cpu_usage_limit>
   <daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
   <daily_xfer_period_days>0</daily_xfer_period_days>
   <day_prefs>
      <day_of_week>0</day_of_week>
      <start_hour>0.00</start_hour>
      <end_hour>24.00</end_hour>
   </day_prefs>
   <day_prefs>
      <day_of_week>1</day_of_week>
      <start_hour>0.00</start_hour>
      <end_hour>24.00</end_hour>
      <net_start_hour>0.00</net_start_hour>
      <net_end_hour>24.00</net_end_hour>
   </day_prefs>
   <day_prefs>
      <day_of_week>2</day_of_week>
      <start_hour>0.00</start_hour>
      <end_hour>24.00</end_hour>
      <net_start_hour>0.00</net_start_hour>
      <net_end_hour>24.00</net_end_hour>
   </day_prefs>
   <day_prefs>
      <day_of_week>3</day_of_week>
      <net_start_hour>0.00</net_start_hour>
      <net_end_hour>24.00</net_end_hour>
   </day_prefs>
</global_preferences>

 

[Ken g6]

Checkpoint frequency is supposed to be controlled by that <disk_interval> line in global_prefs_override.xml. PPS Sieve, for one, respects it. Some other projects don't. 🙁 I recall one guy actually being surprised that this line limited when his PPS Sieve clients checkpointed!