docs: add release note for optional migration

This commit is contained in:
yyforyongyu 2022-05-06 16:40:17 +08:00
parent ac6e1a836c
commit d391514815
No known key found for this signature in database
GPG key ID: 9BCD95C4FF296868
2 changed files with 18 additions and 1 deletions

View file

@ -454,4 +454,4 @@ gRPC performance metrics (latency to process `GetInfo`, etc)](https://github.com
* Torkel Rogstad
* Vsevolod Kaganovych
* Yong Yu
* Ziggie
* Ziggie

View file

@ -30,6 +30,23 @@
* [Delete failed payment attempts](https://github.com/lightningnetwork/lnd/pull/6438)
once payments are settled, unless specified with `keep-failed-payment-attempts` flag.
* [A new db configuration flag
`db.prune-revocation`](https://github.com/lightningnetwork/lnd/pull/6469) is
introduced to take the advantage enabled by [a recent space
optimization](https://github.com/lightningnetwork/lnd/pull/6347). Users can
set this flag to `true` to run an optional db migration during `lnd`'s
startup. This flag will prune the old revocation logs and save them using the
new format that can save large amount of disk space.
For a busy channel with millions of updates, this migration can take quite
some time. The benchmark shows it takes roughly 70 seconds to finish a
migration with 1 million logs. Of course the actual time taken can vary from
machine to machine. Users can run the following benchmark test to get an
accurate time it'll take for a channel with 1 millions updates to plan ahead,
```sh
cd ./channeldb/migration30
go test -bench=. -run=TestMigrateRevocationLogMemCap -benchtime=1000000x -timeout=10m -benchmem
```
## Documentation
* [Add minor comment](https://github.com/lightningnetwork/lnd/pull/6559) on