beck
beck
> MaxConcurrentReadyFetches I think this variable can control the concurrency of reading data. After actually using it, it has no effect, and the problem is reopened.
```bash root@hostname:~# ps -ef |grep boost root 28607 300608 0 17:09 pts/7 00:00:00 grep --color=auto boost root 141437 1 99 11:07 pts/3 07:00:41 boostd -vv run root@hostname:~# lsof -n -p...
`MaxConcurrencyStorageCalls = 100` This variable also looks useless
> > They have stored all data on their own miners without making any progress on distribution, as evidenced here: #1068. Please let us know if we can help with...
Please submit evidence.
 It is just because `StateMinerAvailableBalance` also takes into account the locked positions to be released, `types.BigAdd(abal, vested)`
This problem will occur when `--max-sectors` is less than 2349.
Because the original batch operation unit is 2349, and it was CC before, the gas consumption is not that much, and the normal renewal is also more than 2349 sectors,...