Cap nAttempts penalty at 8 and switch to pow instead of a division loop. #6029

1. 
   gmaxwell commented at 6:52 pm on April 19, 2015: contributor

   On hosts that had spent some time with a failed internet connection their nAttempts penalty was going through the roof (e.g. thousands for all peers) and as a result the connect search was pegging the CPU and failing to get more than a 4 connections after days of running (because it was taking so long per try).
2. Cap nAttempts penalty at 8 and switch to pow instead of a division loop.

   On hosts that had spent some time with a failed internet connection their
    nAttempts penalty was going through the roof (e.g. thousands for all peers)
    and as a result the connect search was pegging the CPU and failing to get
    more than a 4 connections after days of running (because it was taking so
    long per try).

   a784f90c98
3. gmaxwell added this to the milestone 0.10.0 on Apr 19, 2015
4. 
   laanwj commented at 11:46 am on April 20, 2015: member

   Makes sense, utACK
5. laanwj merged this on Apr 20, 2015
6. laanwj closed this on Apr 20, 2015

   ---

7. laanwj referenced this in commit 71900b4426 on Apr 20, 2015
8. 
   laanwj commented at 12:00 pm on April 20, 2015: member

   Cherry-picked to 0.10 as 139cd8177be4895f8b4c2befee35030bdf96132
9. gmaxwell referenced this in commit 139cd8177b on Apr 20, 2015
10. reddink referenced this in commit cc13dbf71c on May 27, 2020
11. DrahtBot locked this on Sep 8, 2021

Contributors
gmaxwell laanwj

Milestone
0.10.0