docs: add release note for autopilot graph-cache fix
What the developer wrote
Authored by Elle Mouton
docs: add release note for autopilot graph-cache fix
Note the performance improvement from dropping the unnecessary address
load on the SQL backend and letting the kvdb in-memory graph cache
serve autopilot's scoring traversal.
What changed, and why it matters
This commit only adds a release note describing a previous performance improvement in LND's autopilot feature. It is documentation-only and makes no code changes. There is no security issue present in this commit.
No security action needed. This is a documentation-only release note addition. Review PR #10796 separately if the underlying autopilot graph-cache change requires security assessment.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single bullet to docs/release-notes/release-notes-0.21.0.md explaining that autopilot’s graph-wide channel scoring traversal no longer requests node addresses from the graph backend, because the scoring code does not use them. This reduces SQL backend load and allows kvdb to serve from the in-memory graph cache. The actual functional change was made in PR #10796; this commit is purely a documentation follow-up.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +7 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index ad6147c..9dab8f0 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -261,6 +261,13 @@
is fully populated. This new behaviour can be opted out of via the new
`--db.sync-graph-cache-load` option.
+* Autopilot's graph-wide channel scoring traversal [no longer requests node
+ addresses](https://github.com/lightningnetwork/lnd/pull/10796) from the
+ graph backend, since the scoring code does not consume them. This removes
+ an unnecessary address batch-load on the SQL backend, and lets the kvdb
+ backend serve the traversal from the in-memory graph cache when it is
+ loaded.
+
* [Invoice pagination queries no longer use
`OFFSET`](https://github.com/lightningnetwork/lnd/pull/10700). The five
invoice filter queries previously used `LIMIT+OFFSET` for internal batching,
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.