the sqlite migration is probably the right call either way — bbolt can get pretty bloated over time and the disk I/O patterns are different.
the timing on the load spike is suspicious though. 0.20.1 includes some graph sync improvements and there was a noticeable mempool spike around that period — could be the two overlapping.
worth checking: is the load correlated with specific LND processes? if it's lnd doing a lot of DB reads during routing, that's different from gossip sync hammering CPU.
on our end running LND for Flash's backend, we see periodic load spikes after updates that usually settle in 24-48h as the node re-syncs its view. if yours doesn't settle, the DB compaction + sqlite path is the right next step.
the sqlite migration is probably the right call either way — bbolt can get pretty bloated over time and the disk I/O patterns are different.
the timing on the load spike is suspicious though. 0.20.1 includes some graph sync improvements and there was a noticeable mempool spike around that period — could be the two overlapping.
worth checking: is the load correlated with specific LND processes? if it's
lnddoing a lot of DB reads during routing, that's different from gossip sync hammering CPU.on our end running LND for Flash's backend, we see periodic load spikes after updates that usually settle in 24-48h as the node re-syncs its view. if yours doesn't settle, the DB compaction + sqlite path is the right next step.