Sorry, I don't understand. From what I found in the wiki trickle messages are
from the application to the server and vice-versa.
We need the clients to contact the server and ask for work every few minutes.
What I understand is that work is only given to clients when they ask for it.
The issue with 7.0.25 is that when there is no work the clients start taking
longer and longer time to ask for work. Then, when there is work the clients
maybe waiting hours before asking for it.
Patricio.
yoyo
<yoyo@mailueberfall
.de> To
Patricio Vidal
08/09/2012 03:35 PM <[email protected]>
cc
[email protected],
[email protected],
[email protected]
Subject
Re: [boinc_dev] Changes to client
scheduler from 6.12.33 to 7.0.25?
For what reason should the client contact the server so often?
You just can use trickle messages to be sent by the client.
yoyo
Patricio Vidal schrieb:
Yes, for our project we need the clients to contact the server every few
minutes. We send jobs that last from 20 minutes to few hours. If the
clients
don't contact the server for several hour then we are in trouble.
Regards,
Patricio.
John.McLeod@sybase.
com
To
08/09/2012 11:21 AM Patricio Vidal
<[email protected]>
cc
[email protected],
[email protected]
Subject
Re: [boinc_dev] Changes to client
scheduler from 6.12.33 to 7.0.25?
It was removed in order to avoid hammering projects from clients that were
not going to ask for work and had no work they were working on.
Perhaps, the code could be modified slightly again. Only ignore the
setting for contact server every X if the client has no work from the
server and the client would not ask for work from the project.
BTW, a really short contact period will play havoc with multi project
clients as they will not be able to get work from elsewhere while you have
no work.
jm7
|------------>
| From: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|Patricio Vidal <[email protected]>
|
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|<[email protected]>
|
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|08/09/2012 11:00 AM
|
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|[boinc_dev] Changes to client scheduler from 6.12.33 to 7.0.25?
|
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|<[email protected]>
|
--------------------------------------------------------------------------------------------------------------------------------------------------|
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.
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.
--
Rate Me, MySkype (yoyo_rkn)Skype Me?! , myICQ 139003243 , myIRC Rechenkraft.net
e.V. - Verein zur Förderung von Bildung, Forschung und Wissenschaft durch
Einsatz vernetzter Computer
weitere interessante Projekte und Hilfe auf unserer Webseite www.Rechenkraft.net
und im Chat
Rechenkraft.net e.V. - Non-profit association for the promotion of education,
research and science through the use of networked computers
other interesting projects and help on our website www.Rechenkraft.net and on
IRC
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.
