I've noticed a few times that when trying to get a new WU after completing one that sometimes the connection fails (for one reason or another, it's not specified) and there is a count down timer for the next attempt...i have also noticed that with each attempt the timer increases almost exponentionally...after 11 attempts, the timer for the next attempt is well over an hour, which at the rate i've been folding with my CPU is one quarter of the time it takes to complete most WUs....this seems to be counter productive...i understand that you don't want to us unintentionally DDOS'ing the server, but at the same time a timer of 5 hours after 13 attempts seems a bit much....
so is there a place where i can change this? or is this something that needs to be worked on and put out in a client update? i would think a 20 min max after the first 5 attemps should be enough...i shouldn't have to restart my client because of previous timed out or fail attempts at getting a new WU
i just came home from lunch break, both my CPU and Nvidia card were on timers over 2 hours...i shut down the client and restarted and they both got new WUs instantly...so it proves my point that the long timers are counter productive
attempt timers
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 1996
- Joined: Sun Mar 22, 2020 5:52 pm
- Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21 - Location: UK
Re: attempt timers
There are many threads that discuss this - the search tool will find them if used:)
Normally retries aren't much (if any) of an issue - just with the current expansion of the number of folders outstripping the infrastructures ability to serve out (and collect to some extent) WUs that people are noticing it … Be patient - things will improve … you don't have to restart your client to reset … simply pausing and restarting (after a bit of a pause) the slot will have the same effect … Please don't do this too often (believe the team say not until the retry timer is 3or 4 hours as it just adds to the friendly fire ddos.
Normally retries aren't much (if any) of an issue - just with the current expansion of the number of folders outstripping the infrastructures ability to serve out (and collect to some extent) WUs that people are noticing it … Be patient - things will improve … you don't have to restart your client to reset … simply pausing and restarting (after a bit of a pause) the slot will have the same effect … Please don't do this too often (believe the team say not until the retry timer is 3or 4 hours as it just adds to the friendly fire ddos.
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)