Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 3
|
![]() |
Author |
|
tfmagnetism
Cruncher Joined: Jul 22, 2011 Post Count: 25 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Regarding server download connection timeout times (and subsequent transient HTTP errors ensuing). I counted THREE minutes last night (making it REALLY hard to retry MCM downloads as only "abort transfer" available on BOINC 7.20.2 - never clicked this as assume it aborts the workunit) and have observed at least 12-17 seconds today (typical).
I was thinking last night this would make it really hard to download with "retry now" button ARP workunits. Anyone from Krembil reading please look into. No idea what the optimal timeout time should be but it still seems too long. It was about 4-5 seconds from memory. That's when you get the transient HTTP errors. And I was thinking about discontinuing ARP as it's taking me about an hour of "retry now" to download couple of workunits. I was going to bring another computer online soon but I can't afford to spend another hour on the ARP per day and even more downloading MCM workunits with "retry now" (at least another hour per day). Ideally there would be NO transient errors. I'm assuming it's beyond possibility to tweak the servers so this doesn't happen and is some hardware limitation. If not maybe it can be reduced/optimised? May be some trial and error involved and I'm assuming Krembil has at least one computer running WCG to observe the effects of changes. Anyone else notice this? Or maybe this is Krembil trying out some configuration changes. Anyone got more info or further details please post back! Anyone from Krembil please take note. |
||
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3295 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
WCG is working on these issues. More information .
----------------------------------------AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1944 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Regarding server download connection timeout times (and subsequent transient HTTP errors ensuing). I counted THREE minutes last night (making it REALLY hard to retry MCM downloads as only "abort transfer" available on BOINC 7.20.2 - never clicked this as assume it aborts the workunit) and have observed at least 12-17 seconds today (typical) I don't have a BOINC 7.20.1 running anywhere on hosts immediately accessible to me, but I have never seen that the [Retry Now] button wasn't on the Transfer tab of the BOINC client. And there is always the "Retry pending transfers" option in the "Tools" menu.And yes, "Abort" means exactly that, terminating any transfer and losing everything associated with the marked WU... In general, this overall issue has been discussed ad nauseam at least two years ago, where it was even worse when combined back then with the OPNG WUs, as that created even more connections to the back end servers... Ralf ![]() |
||
|
|
![]() |