Hi@All
I've the newest boinc with seti@home at my compiuter. boince communicats all 5 min with the server in berkley. Could I change the updatetime?
Many Thx

If you mean if you can change:

10/03/2016 23:12:50 | SETI@home | Project requested delay of 303 seconds
10/03/2016 23:12:50 | SETI@home | [sched_op] Deferring communication for 00:05:03
10/03/2016 23:12:50 | SETI@home | [sched_op] Reason: requested by project

The answer is no, you cannot. This is a server imposed limit to stop hosts from effectively running a denial of service attack on the server.

If you mean something else, please try again. Perhaps write it in German.

---

No, the boinc-client communicats with the berkley-server, then is a delay of 05:03 min, how you wrote (this is fully ok). If this 5min gon, the boinc-client immediately communicats with the berkley-server again, without a delay, and so on and on. Every 5 min my PC contact the boinc-server.

Every 5 min my PC contact the boinc-server.

And you can see the reason in Event Log (Ctrl+Shift+E) - maybe something like this:

13/03/2016 19:17:06 SETI@home Requesting new tasks for GPU

This (if BOINC will ask for work) depend on your two Settings for "days of work":
set on web: Computing preferences
or locally: Local preferences

Set e.g. 3+1 days and BOINC will ask for work maybe one time per day
BOINC will also report completed tasks in hour after upload


The question remains why you don't like "Every 5 min my PC contact the boinc-server"
What do you see as bad with that?

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I can't understand, what you mean. My preferences look so: http://prntscr.com/ah1ho2. Where I've to change.

The cache size is set using a local preference.
Using BOINC manager's "advanced" view
=> Options/ Computing preferences => Computing tab

At the bottom, under "Other":
Store at least xx days of work
Store up to an additional yy days of work

xx must be an integer, set to between 4 and 6 - this is the size of your cache
yy can be a decimal number, the smaller the more forced contact that will take place each day - I've found 0.1 to work well. Unless you suffer a very poor internet connection there is little point in going above 1.0

I hope that helps.

Google translate:

Die Cache-Größe wird eine lokale Einstellung verwendet werden .
Mit "Erweitert" nach Ansicht des BOINC -Manager
=> Optionen / Computing -Einstellungen => Computing Registerkarte

An der Unterseite, unter "Sonstiges" :
Speichern mindestens xx Tage Arbeit
Speichern Sie bis zu weitere yy Tage Arbeit

xx muss eine ganze Zahl sein , auf einen Wert zwischen 4 und 6 - das ist die Größe des Caches
yy kann eine Dezimalzahl sein , je kleiner die mehr erzwungener Kontakt, der Ort jeden Tag stattfinden wird - ich habe 0,1 gefunden gut zu funktionieren. Es sei denn, Sie eine sehr schlechte Internet- Verbindung leiden macht es wenig Sinn in gehen über 1,0

Ich hoffe das hilft.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

This is, what I have in my preferenses:
http://prntscr.com/ai50kt

Better post the contents of global_prefs.xml and as it should exist as you're using the local preferences, the contents of global_prefs_override.xml
Both these files can be found in the BOINC data directory, which is by default a hidden directory at C:\Programdata\BOINC\ under Windows Vista and above.

Both XML files can be opened with Notepad. No need for an XML editor.

---

global_prefs.xml:
<global_preferences>
<source_project>http://setiathome.berkeley.edu/</source_project>
<source_scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</source_scheduler>

<mod_time>1458343258</mod_time>
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>1</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>0</suspend_cpu_usage>
<work_buf_min_days>10</work_buf_min_days>
<work_buf_additional_days>10</work_buf_additional_days>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>360</disk_interval>
<disk_max_used_gb>50</disk_max_used_gb>
<disk_min_free_gb>0.1</disk_min_free_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<ram_max_used_busy_pct>100</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100</ram_max_used_idle_pct>
<leave_apps_in_memory>1</leave_apps_in_memory>
<vm_max_used_pct>100</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<venue name="home">
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>1</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>0</suspend_cpu_usage>
<work_buf_min_days>10</work_buf_min_days>
<work_buf_additional_days>10</work_buf_additional_days>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>360</disk_interval>
<disk_max_used_gb>100</disk_max_used_gb>
<disk_min_free_gb>50</disk_min_free_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<ram_max_used_busy_pct>100</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100</ram_max_used_idle_pct>
<leave_apps_in_memory>0</leave_apps_in_memory>
<vm_max_used_pct>100</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
</venue>
<venue name="work">
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>1</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>0</suspend_cpu_usage>
<work_buf_min_days>10</work_buf_min_days>
<work_buf_additional_days>10</work_buf_additional_days>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>360</disk_interval>
<disk_max_used_gb>100</disk_max_used_gb>
<disk_min_free_gb>5</disk_min_free_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<ram_max_used_busy_pct>100</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100</ram_max_used_idle_pct>
<leave_apps_in_memory>1</leave_apps_in_memory>
<vm_max_used_pct>100</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
</venue>
<venue name="school">
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>1</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>0</suspend_cpu_usage>
<work_buf_min_days>0</work_buf_min_days>
<work_buf_additional_days>10</work_buf_additional_days>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>360</disk_interval>
<disk_max_used_gb>100</disk_max_used_gb>
<disk_min_free_gb>50</disk_min_free_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<ram_max_used_busy_pct>100</ram_max_used_busy_pct>
<ram_max_used_idle_pct>100</ram_max_used_idle_pct>
<leave_apps_in_memory>0</leave_apps_in_memory>
<vm_max_used_pct>100</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
</venue>
</global_preferences>

global_prefs_override.xml:
<global_preferences>
<run_on_batteries>1</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>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>1</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>10.000000</work_buf_min_days>
<work_buf_additional_days>10.000000</work_buf_additional_days>
<max_ncpus_pct>100.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
<disk_interval>360.000000</disk_interval>
<disk_max_used_gb>100.000000</disk_max_used_gb>
<disk_max_used_pct>50.000000</disk_max_used_pct>
<disk_min_free_gb>5.000000</disk_min_free_gb>
<vm_max_used_pct>100.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>
<daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
</global_preferences>

<work_buf_min_days>10.000000</work_buf_min_days>
<work_buf_additional_days>10.000000</work_buf_additional_days>

These are totally unnecessary.

Seti has a hard limit of 100 tasks for CPU and 100 tasks per GPU.

The only thing that you'll achieve with Store at least 10 days of work and Store up to an additional 10 days of work is that BOINC will continue to ask for work and that the server will continually tell you you're not going to get any as you've reached the maximum of tasks in progress. You should be able to see this in the event log (CTRL+SHIFT+E).

So, do as BilBg told you and change Store at least 10 days of work to Store at least 3 days of work and Store up to an additional 10 days of work to Store up to an additional 1 day of work. That will calm down BOINC and not ask for work every 5 minutes, to then be told there isn't any.

---

Many Thx.