"requesting X sec of work" is not logical solution
5 Mar 2005 9:34:12 UTC
Topic 188273
(moderation:
it is not BOINC client who should determine how many seconds of new work should be send to it , but rather a BOINC server should be determining it. Client should only report how many sec of work he still has not processed.
Here is why i think so:
I have got work for the next 6 days, then i changed my preferences to connect every 2 days. Upon next connect to the server my BOINC client requested and recieved more work even though it still has enough work for the next 4 days
2005-03-05 11:25:56 [---] Resuming network activity
2005-03-05 11:25:56 [---] May run out of work in 6.00 days; requesting more
2005-03-05 11:26:13 [Einstein@Home] Started upload of H1_0685.4__0685.9_0.1_T14_Test02_2_0
2005-03-05 11:26:24 [---] May run out of work in 6.00 days; requesting more
2005-03-05 11:26:24 [Einstein@Home] Requesting 345281 seconds of work
2005-03-05 11:26:24 [Einstein@Home] Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-03-05 11:26:29 [Einstein@Home] Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-03-05 11:26:29 [Einstein@Home] General preferences have been updated
2005-03-05 11:26:29 [---] General prefs: from Einstein@Home (last modified 2005-03-03 18:15:58)
2005-03-05 11:26:29 [---] General prefs: using your defaults
2005-03-05 11:26:29 [Einstein@Home] Project prefs: using your defaults
2005-03-05 11:26:39 [Einstein@Home] Finished upload of H1_0685.4__0685.9_0.1_T14_Test02_2_0
2005-03-05 11:26:39 [Einstein@Home] Throughput 19147 bytes/sec
"requesting X sec of work" is not logical solution
)
I personally think that the server is too involved in how much work the clients get. I admit in this situation the server had updated prefs that it would have been nice to honor the new prefs. However this will be a rare occurence in normal operating circumstances.
In my opinion the way it should work is the client should request a number of cobblestones and inform the server how long it expects to need to process that work. The server would then only have to check if it is feasable for the that client to be able to complete work before deadline. To me it seems like this scheme would lower the amount of processing the server needs to do since the client would be figuring in the active fraction, number of other projects, work on hand and other modifications to the base queue size.
BOINC WIKI
BOINCing since 2002/12/8
The server has no idea about
)
The server has no idea about how much time you really have avalibale for BOINC and in how many other BOINC projects you participate to which extent (resource share). The only instance who knows about it is the client.
BM
BM