Hello,

I noticed a change in the client scheduler when moving from 6.12.33 to 7.0.25: I
have the <next_rpc_delay> set 180 in the config.xml.

For 6.12.33 the clients contact the server even if there is no work, which is
our desired behavior:

8/8/2012 11:39:09 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 11:42:12 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 11:45:15 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 11:48:18 PM | AlgoGrid | Requesting new tasks for CPU


For 7.0.25, when there are available task the scheduler contacts the server as
expected:

8/8/2012 9:26:33 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 9:27:10 PM | AlgoGrid | Requesting new tasks for CPU

... but when there is no tasks it starts delaying the request exponentially:

8/8/2012 9:49:45 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 10:08:23 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 10:32:36 PM | AlgoGrid | Requesting new tasks for CPU
8/8/2012 11:37:35 PM | AlgoGrid | Requesting new tasks for CPU
8/9/2012 2:59:13 AM | AlgoGrid | Requesting new tasks for CPU
8/9/2012 10:41:06 AM | AlgoGrid | Requesting new tasks for CPU


Is there a new option to force the rpc call even if there is no tasks available?
We need this behavior because our boinc project needs a quick response from the
clients when we schedule a job (we have workunits of about 1 min processing time
and we schedule thousands at a time).

Thank you,
Patricio.


The server  made the following annotations                           

---------------------------------------------------------------------------------

This message contains information that may be privileged or confidential and is 
the property of Beckman Coulter, Inc.  It is intended only for the person to 
whom it is addressed.  If you are not the intended recipient, you are not 
authorized to read, print, retain, copy, disseminate, distribute or use this 
message or any part thereof.  If you receive this message in error, please 
notify the sender immediately and delete all copies of this message.

---------------------------------------------------------------------------------

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to