Skip to content
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 [6] #9555

Merged
merged 3 commits into from
Feb 28, 2025

Conversation

ellemouton
Copy link
Collaborator

@ellemouton ellemouton commented Feb 26, 2025

** Final PR in the cache-RIP series **

This builds towards this final result by building this side branch incrementally.

In this PR, the extraction of the graphCache from the CRUD layer (KVStore) into the ChannelGraph layer is completed.
The opportunity is also taken to move the graphCache population logic out of the constructor of the ChannelGraph and into
a new Start method instead.

@ellemouton ellemouton self-assigned this Feb 26, 2025
Copy link
Contributor

coderabbitai bot commented Feb 26, 2025

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)
  • llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ellemouton ellemouton force-pushed the graph17 branch 2 times, most recently from 7505858 to bb3af46 Compare February 27, 2025 12:02
@ellemouton ellemouton changed the base branch from elle-graphCacheBase2 to elle-graphCacheBase February 27, 2025 12:02
Copy link
Collaborator

@bhandras bhandras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🍫

@@ -119,6 +88,13 @@ func (c *ChannelGraph) Start() error {
log.Debugf("ChannelGraph starting")
defer log.Debug("ChannelGraph started")

if c.graphCache != nil {
if err := c.populateCache(); err != nil {
return fmt.Errorf("could not populate the graph "+
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: the started flag remains dirty, but i think that's okay since we likely won't try to start the same graph instance again.

if !c.started.CompareAndSwap(false, true) {
return nil
}
log.Debugf("ChannelGraph starting")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
log.Debugf("ChannelGraph starting")
log.Debug("ChannelGraph starting")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a pattern for choosing the format when using a simple string, or does it not matter?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as it conveys useful info to the user

Comment on lines +37 to +38
started atomic.Bool
stopped atomic.Bool

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need two booleans (started and stopped) to track the state? Wouldn't a single atomic boolean be enough? Using just one (active, for example) would simplify the logic and prevent inconsistent states like started = true and stopped = true at the same time.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these should be read as "has this service ever been started" and "has this service ever been stopped" . So both being true is legit.

We use this pattern throughout the code-base. Services are not restartable

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need two booleans (started and stopped) to track the state?

Very good question! In addition to Elle's comment I do think using one var makes things easier as it prevents inconsistent states, we may consider changing it one day but it's not our priority atm, plus it's working fine so far.

We do this in preparation for moving channel cache population logic out
of the constructor and into the Start method. We also will later on
(when topology subscription is moved to the ChannelGraph), have a
goroutine that will need to be kicked off and stopped.
…ction

In this commit, we move the graph cache population logic out of the
ChannelGraph constructor and into its Start method instead.
Copy link
Member

@yyforyongyu yyforyongyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹

@@ -184,13 +184,12 @@ const (
type KVStore struct {
db kvdb.Backend

// cacheMu guards all caches (rejectCache, chanCache, graphCache). If
// cacheMu guards all caches (rejectCache and chanCache). If
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

}

// The graph cache can be turned off (e.g. for mobile users) for a
// speed/memory usage tradeoff.
graphCache := NewGraphCache(opts.preAllocCacheNumNodes)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🌟

Comment on lines +37 to +38
started atomic.Bool
stopped atomic.Bool
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need two booleans (started and stopped) to track the state?

Very good question! In addition to Elle's comment I do think using one var makes things easier as it prevents inconsistent states, we may consider changing it one day but it's not our priority atm, plus it's working fine so far.

@yyforyongyu
Copy link
Member

btw the itest update_channel_policy is now flaky - I think for intermediate PRs merged to a side branch it's fine, but eventually when we merge them back to the master we would need to make sure the CI stays green🙏

@ellemouton
Copy link
Collaborator Author

ellemouton commented Feb 28, 2025

btw the itest update_channel_policy is now flaky

Investigating 👍 (looks like [5] introduced it) nvm - i think it was pre-existing. I'm going to merge this into the side branch and then open 1 more PR to the side branch to fix the flake

@ellemouton ellemouton merged commit 1293f2e into lightningnetwork:elle-graphCacheBase Feb 28, 2025
31 of 35 checks passed
@ellemouton ellemouton deleted the graph17 branch February 28, 2025 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants