BOINC Client 5.10.45 is not reporting COMPLETED TASKS to project servers within minutes and holds them in local task queue unsent extremely long!

[ranger911]

Hi,

I participate in 4 projects - WCG, Climate, Rosetta, MalariaControl?. I noticed the following WRONG (to my best knowledge) behaviour of BOINC client (5.10.45 at all PCs):

Environment: Windows XP SP2/SP3, 20+ different PCs, everywhere is permanent connection to the Internet witn no limits at Proxies/Firewalls?, BOINC client can connect always (24h, no limits), configuration for "ahead task buffer" = 10 days Please see attached screenshots for my client settings details...

PROBLEM DESCRIPTION:

---

When task is complete, BOINC says "task complete" and won't send it to project server for any projects (no matter) I participate in for long time. I see wrong scheduling policy, as all completed tasks should be reported, uploaded and confirmed then removed as complete out of local BOINC task list immediately upon completion or within quite short period of time (minutes). Completed tasks even far ahead of deadline (e.g. few days ahead) should NOT be kept at client side, and should be accepted by server (and removed from BOINC tasklist) immediately upon completion (as fast as possible - within minutes since complete).

At that moment, each completed task for ANY project may hold in "complete state" non-reported and non-uploaded to respective project server very long, up to few days.

The only way I see to push it - manually hit UPDATE button to manually start sync process of each local BOINC client queue with respective project server.

I believe this is software code issue, not settings, and I'd be happy, if above info would be fixed. If this is a settings issue, please give me idea what is wrong with my settings and how to fix it.

Thank you, Maxim Bocharov MARSNET

[Ageless]

This is normal behaviour, it is not a bug.

For BOINC 5.8 and above: Completed work is reported at the first of:

1) 24 hours after completion (was Connect every X after completion).
2) 24 hours before report is due.
3) Connect every X before report is due.
4) On a trickle up message (CPDN only so far).
5) On a request for more work.
6) On a manual update.

[ranger911]

Hi,

I understand the reasons, but:

Well, OKAY, what shall I do now??? I would like to be sure all completed tasks are reported as quick as possible, probably in much less time period, than 24 hrs.

What setting to change to let BOINC client try to connect and to report e.g. say each 1 hr to upload all the stuff he has already completed in the queue...

PLEASE COPY..!? Maxim

[Der Meister]

There is no reason for doing this. The client already ensures that it reports all results in time (if this is possible). And the delay is there for a reason: Every scheduler request implies some load on the server, especially if reporting results. Reporting multiple results at once is more efficient than reporting each result separately. Therefore this delay can help to reduce the server load which is really important. That's why the client is implemented this way and I see no reason why this behaviour should be changed.

[davea]

Use the <report_results_immediately> option (in cc_config.xml)