-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graph: extract cache from CRUD [4] #9551
graph: extract cache from CRUD [4] #9551
Conversation
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just one comment re pruning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🏄
And update cache outside the method rather. This will make it easier to completely move the cache write out to the ChannelGraph layer.
Here we move the cache writes for DisconnectBlockAtHeight and DeleteChannelEdges to the ChannelGraph.
In preparation for moving the cache write completely out of KVStore, we move the cache write up one layer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool I think it's good to go, only have a comment about rebasing, the rest are nits so feel free to ignore.
graph/db/graph.go
Outdated
// cacheMu guards any writes to the graphCache. It should be held | ||
// across the DB write call and the graphCache update to make the | ||
// two updates as atomic as possible. | ||
cacheMu sync.Mutex |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this added here already? I guess it's missing a rebase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah - i made it so that all the PRs dont depend on eachother. They all pointed to the same base. So now that that other one got in first, i can remove that here.
ie, wanted to have all the PRs disjoint
return err | ||
} | ||
|
||
if c.graphCache != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
think we can use if c.graphCache == nil
and exit early to save some indentations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah ok so for this i think better to keep as is since yes today it exits after, but we will soon expand ChannelGraph to do more than just handle the graphCache. For example when we start moving topology management here and remote graph handling
return nil, err | ||
} | ||
|
||
if c.graphCache != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same nit re exiting early.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see above reply
graph/db/kv_store.go
Outdated
return err | ||
} | ||
|
||
if c.graphCache != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
starting to get a bit lost here...so I guess the goal is to keep KVStore
oblivious of the existence of the graph cache, so I guess we need to move the cache into an even higher layer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is an intermediary step. the very next commit does this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see commit message "in preparation for moving cache up.."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
saw your other comment now :)
@@ -1509,19 +1493,18 @@ func (c *KVStore) PruneGraphNodes() error { | |||
return ErrGraphNoEdgesFound | |||
} | |||
|
|||
prunedNodes, err := c.pruneGraphNodes(nodes, edgeIndex) | |||
var err error | |||
prunedNodes, err = c.pruneGraphNodes(nodes, edgeIndex) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok i see it's done in a different commit.
} | ||
|
||
if c.graphCache != nil { | ||
for _, edge := range edges { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is future stuff, but I just realized all these logic can live in graphCache
instead, sth like graphCache.pruneGraph
. And same for other places where we have customized logic for the cache.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah agreed 👍
This commit moves the cache writes for PruneGraphNodes and PruneGraph from the KVStore to the ChannelGraph.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
aafbc98
into
lightningnetwork:elle-graphCacheBase
** PR 4 ** (note: not dependent on PR 3)
This builds towards this final result by building this side branch incrementally.
In this PR, we move the cache writes for
DeleteChannelEdges
,DisconnectBlockAtHeight,
PruneGraphand
PruneGraphNodes` from the KVStore to the ChannelGraph. These each need a bit of refactoring of somehelper methods first, so this PR does this refactoring too.