Why the 364 second delay after upload completed task before can report the completed task?
Message boards :
Number crunching :
Why the 364 second delay after upload completed task before can report the completed task?
Message board moderation
| Author | Message |
|---|---|
 Send message Joined: 21 Jun 24 Posts: 12 Credit: 231,598 RAC: 937 |
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 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  
|
 goofyx[BOINC@Poland]Send message Joined: 12 Jun 24 Posts: 93 Credit: 154,062,356 RAC: 218,729  |
I decrease this time from 360s to 60s |
 Send message Joined: 1 Jul 24 Posts: 8 Credit: 28,630 RAC: 72 |
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. 
|
|
goofyx[BOINC@Poland] Send message Joined: 12 Jun 24 Posts: 93 Credit: 154,062,356 RAC: 218,729 |
next_rpc_delay increase to 3700 |
|
Send message Joined: 1 Jul 24 Posts: 8 Credit: 28,630 RAC: 72 |
next_rpc_delay increase to 3700Perfect, now the log does not show any unnecessary activities anymore.
|
©2024 Goofyx Prodakszyn