Why the 364 second delay after upload completed task before can report the completed task?

Author	Message
Dr Who Fan Send message Joined: 21 Jun 24 Posts: 17 Credit: 344,358 RAC: 822	Message 246 - Posted: 23 Sep 2024, 11:35:49 UTC As title says... Why is there a 364 second delay after upload completed task before can report task as completed? SEEMS LIKE A WASTE OF TIME/BANDWIDTH/SERVER RESOURCES. Most projects wait a few seconds at most to finish this last step. 9/23/2024 06:01:27 \| \| [http_xfer] [ID#1] HTTP: wrote 2833 bytes 9/23/2024 06:01:27 \| goofyxGrid@Home NCI \| [http] [ID#1] Info: Connection #3549 to host nci.boinc.goofyx.pl left intact 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| [file_xfer] http op done; retval 0 (Success) 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| [file_xfer] parsing upload response: <data_server_reply> <status>0</status></data_server_reply> 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| [file_xfer] parsing status: 0 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| [file_xfer] file transfer status 0 (Success) 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| Finished upload of test_S000327_N000486_M100000.in_0_r759118600_0 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| [file_xfer] Throughput 452 bytes/sec 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| Scheduler request completed 9/23/2024 06:01:28 \| goofyxGrid@Home NCI \| Project requested delay of 364 seconds I can manually request a project update to force it to finish the process with no probelm... 9/23/2024 06:02:46 \| goofyxGrid@Home NCI \| update requested by user 9/23/2024 06:02:49 [goofyxGrid@Home NCI] Sending scheduler request: Requested by user. 9/23/2024 06:02:49 [goofyxGrid@Home NCI] Reporting 1 completed tasks ID: 246 · Rating: 0 · rate: / Reply Quote

goofyx[BOINC@Poland] Project administrator Project developer Project tester Send message Joined: 12 Jun 24 Posts: 94 Credit: 164,517,586 RAC: 5,569	Message 247 - Posted: 23 Sep 2024, 13:32:34 UTC I decrease this time from 360s to 60s ID: 247 · Rating: 0 · rate: / Reply Quote

Link Send message Joined: 1 Jul 24 Posts: 10 Credit: 28,660 RAC: 0	Message 248 - Posted: 23 Sep 2024, 19:20:18 UTC - in response to Message 247. You could also remove <next_rpc_delay>1800.000000</next_rpc_delay> or at least increase it to something like 3700, connecting to the server every 30 minutes for nothing does not really make much sense IMHO. ID: 248 · Rating: 0 · rate: / Reply Quote

goofyx[BOINC@Poland] Project administrator Project developer Project tester Send message Joined: 12 Jun 24 Posts: 94 Credit: 164,517,586 RAC: 5,569	Message 249 - Posted: 24 Sep 2024, 6:16:27 UTC Last modified: 24 Sep 2024, 6:16:38 UTC next_rpc_delay increase to 3700 ID: 249 · Rating: 0 · rate: / Reply Quote

Link Send message Joined: 1 Jul 24 Posts: 10 Credit: 28,660 RAC: 0	Message 253 - Posted: 28 Sep 2024, 10:23:22 UTC - in response to Message 249. next_rpc_delay increase to 3700 Perfect, now the log does not show any unnecessary activities anymore. ID: 253 · Rating: 0 · rate: / Reply Quote