How do I increase the time interval from 5 minutes to say 12 or 15 minutes?


Zalster

How do I increase the time interval from 5 minutes to say 12 or 15 minutes?


Zalster

I've always wondered about this too. There may be a way in some Boinc core file to increase it, but likely not decrease it. Unless it's hard coded in the Boinc manager - that's my guess.

---

The minimum is set by the project's configuration:

<min_sendwork_interval> N </min_sendwork_interval>
Minimum number of seconds between sending jobs to a given host. You can use this to limit the impact of faulty hosts.

This project has 300 seconds there, BOINC scales it by 1.01 to ensure even a clock running fast won't cause a host to ask again too soon, so the scheduler reply specifies a 303 second delay.

Setting the "additional" work buffer slightly higher would cause fewer work fetch attempts on average, but attempts which fail to get as as much work as requested would still cause another attempt 303 seconds later. Attempts which fail to get any reply of course have a backoff added.

Perhaps using a script to turn BOINC network activity on and off with a cycle of 10 or 12 minutes could produce the desired effect. If downloads for a successful work request can all be completed within 4 minutes, a 4 minute on followed by 6 minutes off cycle would effectively make the minimum request interval 10 minutes.

                                                                  Joe

I've found some projects you have to keep the network in BOINC active for them to operate. So I've been trying to work out how to do this as well.

So far the only way I have found is to use boinccmd in a batch file like this:

set sleeptime=900
:start
boinccmd --project http://setiathome.berkeley.edu/ allowmorework
boinccmd --project http://setiathome.berkeley.edu/ update
timeout 180 /NOBREAK
boinccmd --project http://setiathome.berkeley.edu/ nomorework
timeout %sleeptime% /NOBREAK
goto start

I think adding the option in BOINC for <min_tasks_reported>N</min_tasks_reported> might be a more ideal solution to keep a host from hammering a project at its sendwork interval.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[