Hi, thank you for your help

- If you open the BOINCmgr and look in the Activity menu, what does it say for the network setting.... Always Available, Per Schedule, or Network Suspended?
I've got "per schedule", but I also tried "always available" for few days without any kind of change.

- Does it get new work automatically after sitting around for minutes, or are you hitting the Update button in the Projects Tab to get things moving?
He taks new WU's but long time after finished the WU's in the list. So during long minutes maybe more, it just don't work anymore. When I hit update button It send finished work and take some new wu's.

global_prefs.xml
- <global_preferences>
<source_project>http://www.worldcommunitygrid.org/</source_project>
<source_scheduler>https://secure.worldcommunitygrid.org/boinc/w...</source_scheduler>
<mod_time>1189604391</mod_time>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>60.0</disk_interval>
<disk_max_used_gb>2.0</disk_max_used_gb>
<disk_max_used_pct>75.0</disk_max_used_pct>
<disk_min_free_gb>0.1</disk_min_free_gb>
<idle_time_to_run>0.5</idle_time_to_run>
<max_bytes_sec_down>0.0</max_bytes_sec_down>
<max_bytes_sec_up>0.0</max_bytes_sec_up>
<max_cpus>4</max_cpus>
<run_if_user_active />
<vm_max_used_pct>75.0</vm_max_used_pct>
<work_buf_min_days>0.2</work_buf_min_days>
<end_hour>0</end_hour>
<net_end_hour>0</net_end_hour>
<net_start_hour>0</net_start_hour>
<start_hour>0</start_hour>
<cpu_usage_limit>100.0</cpu_usage_limit>
<ram_max_used_busy_pct>100.0</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100.0</ram_max_used_idle_pct>
- <venue name="home">
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>60.0</disk_interval>
<disk_max_used_gb>2.0</disk_max_used_gb>
<disk_max_used_pct>75.0</disk_max_used_pct>
<disk_min_free_gb>0.1</disk_min_free_gb>
<end_hour>0</end_hour>
<idle_time_to_run>0.5</idle_time_to_run>
<max_bytes_sec_down>0.0</max_bytes_sec_down>
<max_bytes_sec_up>0.0</max_bytes_sec_up>
<max_cpus>4</max_cpus>
<net_end_hour>0</net_end_hour>
<net_start_hour>0</net_start_hour>
<run_if_user_active />
<start_hour>0</start_hour>
<vm_max_used_pct>75.0</vm_max_used_pct>
<work_buf_min_days>0.5</work_buf_min_days>
<cpu_usage_limit>100.0</cpu_usage_limit>
<ram_max_used_busy_pct>100.0</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100.0</ram_max_used_idle_pct>
</venue>
</global_preferences>

global_prefs_override.xml

- <global_preferences>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>0</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>0.200000</work_buf_min_days>
<work_buf_additional_days>0.250000</work_buf_additional_days>
<max_cpus>4</max_cpus>
<cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>2.000000</disk_max_used_gb>
<disk_max_used_pct>75.000000</disk_max_used_pct>
<disk_min_free_gb>0.100000</disk_min_free_gb>
<vm_max_used_pct>75.000000</vm_max_used_pct>
<ram_max_used_busy_pct>100.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100.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>
</global_preferences>

client_state.xml

- <time_stats>
<on_frac>1.000000</on_frac>
<connected_frac>-1.000000</connected_frac>
<active_frac>0.000000</active_frac>
<cpu_efficiency>0.944150</cpu_efficiency>
<last_update>2167229413.104599</last_update>
</time_stats>

Don't hesitate to ask me for more information, thank again.

My values :
<resource_share>100.000000</resource_share>
<duration_correction_factor>1.157697</duration_correction_factor>

I'am going to try to change the value active_frac to 1.000000 now.
Thanks

Good Sekaiji,

Reading around, think that at one point in time you had situation developing where BOINC got into panic thinking it was not going to make 1 or more deadlines (did you have e.g. CPDN in past?). When it gets in that state, it keeps adjusting the active_frac down. There's some bug also loitering that they've not been able to fix. Essentially once extreme values like 0.00000 or -1.00000 are reached they never get right again.

Anyhow, while you now know how to tweak it, keep the hands *off* from that file, as it is the housekeeping boss of BOINC. The global prefs should not be changed every day.... it likes to be left alone after which it can take weeks for BOINC to figure out on what legs its standing.

bon soir