[qa] Use cached utxo set to fix performance regression #9274

1. 
   MarcoFalke commented at 6:24 PM on December 4, 2016: member

   I removed the caching in #9221, which made pruning take longer.

   Credit goes to @morcos for quickly raising the issue: #9221 (comment)

2. MarcoFalke added the label Tests on Dec 4, 2016
3. MarcoFalke added this to the milestone 0.14.0 on Dec 4, 2016
4. MarcoFalke assigned MarcoFalke on Dec 4, 2016
5. [qa] pruning: Use cached utxo set to run faster fa2ecc48fb
6. MarcoFalke force-pushed on Dec 4, 2016
7. 
   morcos commented at 9:24 PM on December 4, 2016: member

   what about fixing maxuploadtarget.py i think it also got slower?

8. [qa] maxuploadtarget: Use cached utxo set fab1af31d4
9. 
   MarcoFalke commented at 11:43 PM on December 4, 2016: member

   Not as significant, but gives back about 10 seconds, why not.

10. MarcoFalke renamed this:
    [qa] pruning: Use cached utxo set to run faster
    [qa] Use cached utxo set to fix performance regression
    on Dec 5, 2016
11. 
    morcos commented at 8:43 PM on December 5, 2016: member

    ACK

    Thanks.

12. MarcoFalke merged this on Dec 6, 2016
13. MarcoFalke closed this on Dec 6, 2016

    ---

14. MarcoFalke referenced this in commit 919db037f1 on Dec 6, 2016
15. MarcoFalke deleted the branch on Dec 6, 2016
16. codablock referenced this in commit d7b2834f79 on Jan 16, 2018
17. codablock referenced this in commit cfd15237a4 on Jan 16, 2018
18. codablock referenced this in commit 19958fecf9 on Jan 17, 2018
19. andvgal referenced this in commit dafda43766 on Jan 6, 2019
20. CryptoCentric referenced this in commit 4f6119c63d on Feb 25, 2019
21. MarcoFalke locked this on Sep 8, 2021

Contributors

MarcoFalkemorcos

Milestone
0.14.0