Pirates@Home logo

Pirates@Home

Berkeley Open Infrastructure
BOINC!
for Network Computing
Home Help Status Forums Glossary Account

Longer communication deferrals while in port

log in

Advanced search

Message boards : Wish list : Longer communication deferrals while in port

Author Message
Profile Odysseus
Volunteer tester
Avatar
Send message
Joined: 20 Aug 06
Canada
Team Canada
Credit: 1,777.8
RAC: 0.00
Joined: Aug 20, 2006
Verified: Sep 30, 2009
Dubloons: 3
Pieces of Eight: 5
Punishment: Aztec curse
Message 8115 - Posted: 6 Dec 2008 | 5:44:18 UTC

I’ve noticed that me hosts generate frequent traffic tryin’ t’ get work, often wit’ only a few minutes between requests. No big deal, but it clutters up th’ logs. Moreover th’ crew are beginnin’ t’ resent constant watch rotations while they might as well be on shore-leave …

Would it be possible t’ get th’ server t’ issue one-day (or longer) deferrals when thar are no raids in th’ offin’?

____________

Was that a Siren I heard?

Profile Pooh Bear 27
Volunteer tester
Avatar
Send message
Joined: 7 Sep 08
United States
The Knights Who Say Ni!
Credit: 7,851.4
RAC: 0.00
Joined: Sep 7, 2008
Verified: Jul 4, 2011
Dubloons: 3
Pieces of Eight: 6
Punishment: Misfit
Message 8117 - Posted: 6 Dec 2008 | 11:05:02 UTC

If I understand it correctly, it's an algorithm built into the BOINC software, and the projects cannot influence it.

____________

Profile Ageless
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 20 Jul 04
Netherlands
Machinae Supremacy
Credit: 1,295.9
RAC: 0.00
Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Cat o' Nine Tails
Message 8119 - Posted: 6 Dec 2008 | 13:47:09 UTC - in response to Message 8117.

It's both.

Older clients did it themselves, newer clients get the deferral from the server, set through the <next_rpc_delay>x</next_rpc_delay>

In each scheduler reply, tell the clients to do another scheduler RPC after at most X seconds, regardless of whether they need work. This is useful, e.g., to ensure that in-progress jobs can be canceled in a bounded amount of time.

Newer meaning 5.10 and above.
____________
Jord.

The BOINC FAQ Service.

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,009.8
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8120 - Posted: 6 Dec 2008 | 15:00:07 UTC - in response to Message 8119.

Ageless wrote:

Older clients did it themselves, newer clients get the deferral from the server, set through the <next_rpc_delay>x</next_rpc_delay>

Except that I think the meanings are slightly different. What the Mad Toms are talking about is a signal that they don't have to come back for a while. A lower bound on the delay. Setting next_rpc_delay tells the client an upper bound on the delay -- you must try to be back for more work within this time span. It's to allow canceling jobs if needed, and could also be used for "low latency" tasks.

So I think we are talking about two different things. But I've set next_rpc_delay to 1 hour just to try it out. That may make it worse for Tom, not better, but we'll see what happens.

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Pooh Bear 27
Volunteer tester
Avatar
Send message
Joined: 7 Sep 08
United States
The Knights Who Say Ni!
Credit: 7,851.4
RAC: 0.00
Joined: Sep 7, 2008
Verified: Jul 4, 2011
Dubloons: 3
Pieces of Eight: 6
Punishment: Misfit
Message 8121 - Posted: 6 Dec 2008 | 17:06:18 UTC

Just testing this, with a request for work, it then took me to 1 minute, 2 minutes, 15 minutes. So I think the setting you set will only allow for a maximum of 1 hour, as I had one that was on a 4 hour one that I started testing this with.

I can not be positive that it's the maximum, but I can say for sure it's not minimum (running 6.2.18).

____________

Profile Odysseus
Volunteer tester
Avatar
Send message
Joined: 20 Aug 06
Canada
Team Canada
Credit: 1,777.8
RAC: 0.00
Joined: Aug 20, 2006
Verified: Sep 30, 2009
Dubloons: 3
Pieces of Eight: 5
Punishment: Aztec curse
Message 8122 - Posted: 6 Dec 2008 | 20:19:44 UTC

I’ve seen 24-hour deferrals from other projects without work for me host. BOINC v5.10.x doesn’€™t log deferral times th’ way some older versions did, so I can nah check back, but I’ve certainly observed it recently from Docking@home (which has no current PPC app—since ’tis only once a day I let me G5 nag instead o’ suspendin’ it) ’n from SETI@home Beta (fer most o’ this week I couldn’t get AstroPulse work). I dunno wha’ circumstances trigger this behaviour. I ’ave also observed that repeated connection failures can prompt one-week deferrals.

Profile Ageless
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 20 Jul 04
Netherlands
Machinae Supremacy
Credit: 1,295.9
RAC: 0.00
Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Cat o' Nine Tails
Message 8123 - Posted: 7 Dec 2008 | 0:21:02 UTC
Last modified: 7 Dec 2008 | 0:22:45 UTC

Mine did:

07-Dec-08 00:23:46|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 00:24:51|Pirates@Home|[sched_op_debug] Deferring communication for 2 min 17 sec
07-Dec-08 00:27:16|Pirates@Home|[sched_op_debug] Deferring communication for 4 min 51 sec
07-Dec-08 00:32:17|Pirates@Home|[sched_op_debug] Deferring communication for 3 min 39 sec
07-Dec-08 00:36:03|Pirates@Home|[sched_op_debug] Deferring communication for 25 min 27 sec
07-Dec-08 01:01:36|Pirates@Home|[sched_op_debug] Deferring communication for 55 min 34 sec

I think the 24 hour and one week deferrals were in the client, at least in 5.4 and 5.8 clients, if the project could not be found the client would automatically defer for 24 hours to a week. If I am not mistaken, taking the scheduler down will automatically give the maximum deferral time to the client that's trying to make contact with the project.

As for the 'new use' of [next_rpc_delay] look at changeset 16206, Eric.
(Although this may only be in use in the latest back-end version and the 6.3 and 6.4 clients, especially since this change was made only 2 months ago)
____________
Jord.

The BOINC FAQ Service.

Profile code { dwarf }
Avatar
Send message
Joined: 20 Jan 07
Poland
Credit: 709.5
RAC: 0.00
Joined: Jan 20, 2007
Verified: NEVER
Dubloons: 3
Pieces of Eight: 2
Message 8124 - Posted: 7 Dec 2008 | 2:12:06 UTC - in response to Message 8123.

Ageless wrote:

As for the 'new use' of [next_rpc_delay] look at changeset 16206, Eric.


Thanks. This is what I suggested, next_rpc_delay is a maximum delay. But I didn't know that we now had a minimum, request_delay. This is what Tom asked for, a "minimum" for the delay interval before the next contact.

Let's try it out. I'm setting it to 24 hours (and the upper bound at 10 days).

Profile Pooh Bear 27
Volunteer tester
Avatar
Send message
Joined: 7 Sep 08
United States
The Knights Who Say Ni!
Credit: 7,851.4
RAC: 0.00
Joined: Sep 7, 2008
Verified: Jul 4, 2011
Dubloons: 3
Pieces of Eight: 6
Punishment: Misfit
Message 8126 - Posted: 7 Dec 2008 | 15:02:40 UTC - in response to Message 8124.

Let's try it out. I'm setting it to 24 hours (and the upper bound at 10 days).

Yup, looks like you got it. I am getting larger hour push backs than ever before.

Remember to change it back once you get new work in.

____________

Profile Ageless
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 20 Jul 04
Netherlands
Machinae Supremacy
Credit: 1,295.9
RAC: 0.00
Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Cat o' Nine Tails
Message 8128 - Posted: 7 Dec 2008 | 23:17:34 UTC

After today's initial 1 minute deferrals growing slightly, eventually reaching 3 hour+ deferrals, it looks like it's going through a loop:

07-Dec-08 18:43:10|Pirates@Home|[sched_op_debug] Deferring communication for 3 hr 44 min 30 sec
07-Dec-08 22:27:49|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 22:28:49|Pirates@Home|[sched_op_debug] Fetching master file
07-Dec-08 22:28:49|Pirates@Home|Fetching scheduler list
07-Dec-08 22:28:54|Pirates@Home|[sched_op_debug] Got master file; parsing
07-Dec-08 22:28:54|Pirates@Home|[sched_op_debug] Found 1 scheduler URLs in master file
07-Dec-08 22:28:54|Pirates@Home|Master file download succeeded
07-Dec-08 22:29:05|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 22:30:10|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 22:31:16|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 22:32:21|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 22:33:27|Pirates@Home|[sched_op_debug] Deferring communication for 2 min 25 sec
07-Dec-08 22:35:57|Pirates@Home|[sched_op_debug] Deferring communication for 3 min 40 sec
07-Dec-08 22:39:43|Pirates@Home|[sched_op_debug] Deferring communication for 5 min 15 sec
07-Dec-08 22:45:05|Pirates@Home|[sched_op_debug] Deferring communication for 19 min 25 sec
07-Dec-08 23:04:37|Pirates@Home|[sched_op_debug] Deferring communication for 20 min 42 sec
07-Dec-08 23:25:27|Pirates@Home|[sched_op_debug] Deferring communication for 28 min 51 sec
07-Dec-08 23:54:24|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 23:55:24|Pirates@Home|[sched_op_debug] Fetching master file
07-Dec-08 23:55:24|Pirates@Home|Fetching scheduler list
07-Dec-08 23:55:29|Pirates@Home|[sched_op_debug] Got master file; parsing
07-Dec-08 23:55:29|Pirates@Home|[sched_op_debug] Found 1 scheduler URLs in master file
07-Dec-08 23:55:29|Pirates@Home|Master file download succeeded
07-Dec-08 23:55:39|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 23:56:44|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 23:57:50|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
07-Dec-08 23:58:56|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
08-Dec-08 00:00:01|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 49 sec
08-Dec-08 00:01:57|Pirates@Home|[sched_op_debug] Deferring communication for 1 min 39 sec
08-Dec-08 00:03:42|Pirates@Home|[sched_op_debug] Deferring communication for 8 min 16 sec
08-Dec-08 00:12:04|Pirates@Home|[sched_op_debug] Deferring communication for 12 min 14 sec

On my other system it looks like this is the longest deferral it can do, before returning to 1 minute loops:

07-Dec-08 20:45:04|Pirates@Home|[sched_op_debug] Deferring communication for 1 hr 51 min 53 sec


____________
Jord.

The BOINC FAQ Service.

Post to thread

Message boards : Wish list : Longer communication deferrals while in port

Home Help Status Forums Glossary Account


Return to Pirates@Home main page


Copyright © 2013 Capt. Jack Sparrow