Scan backlog confirmation heights in lockstep using crawlers (#5085) Add a confirmation height crawler and use it alongside the account crawler during backlog population. This avoids issuing a separate confirmation height lookup for every account while preserving batch progression.
__________
Type: commit
Hash: 0b848dbf2f1523ab369b9dc8cd654ab90f0e494a
Created: today
__________
gr0v1ty/nano-node:0b848dbf2f1523ab369b9dc8cd654ab90f0e494a
| Test Case | Status | Duration | Median Deviation | Log | Graph |
|---|---|---|---|---|---|
| 5n4pr_conf_10k_bintree | PASS | 110 s | 1.0 s | - | Show |
| 5n4pr_conf_10k_change | PASS | 196 s | 5.5 s | - | Show |
| 5n4pr_conf_change_dependant | PASS | 114 s | 3.5 s | - | - |
| 5n4pr_conf_change_independant | PASS | 109 s | -0.5 s | - | - |
| 5n4pr_conf_send_dependant | PASS | 109 s | -2.0 s | - | - |
| 5n4pr_conf_send_independant | PASS | 106 s | -4.5 s | - | - |
| 5n4pr_rocks_10k_bintree | PASS | 118 s | 4.5 s | - | - |
| 5n4pr_rocks_10k_change | PASS | 188 s | 16.0 s | - | - |