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

feat(cache-store): add deep copy function #20862

Closed
wants to merge 4 commits into from
Closed

Conversation

GAtom22
Copy link
Contributor

@GAtom22 GAtom22 commented Jul 3, 2024

Description

This PR adds a Copy() function to the CacheMultiStore to create a deep copy of the store.

This function is useful to create snapshots of the multi-store while keeping the same CacheMultiStore with its cache entries throughout a transaction lifecycle. Also, it allows to revert changes at a specific point.

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features
    • Added the ability to create deep copies of store objects in the app, enhancing data management and manipulation capabilities.

@GAtom22 GAtom22 requested a review from a team as a code owner July 3, 2024 12:44
Copy link
Contributor

coderabbitai bot commented Jul 3, 2024

Walkthrough

Walkthrough

This change introduces a new Copy() method to the CacheMultiStore and cachekv.Store classes in the store module. The Copy() method allows the creation of deep copies of the store objects, enhancing the management and manipulation capabilities within the Cosmos SDK.

Changes

File(s) Change Summary
store/cachekv/store.go Added Copy method to the Store struct, allowing deep copying of its properties.
store/cachemulti/store.go Added Copy method to the Store struct, enabling deep copy creation of its properties.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

65-65: Ensure consistency in changelog entries.

The added changelog entry is clear and concise. However, it would be more consistent with the rest of the entries if it mentioned the specific files or modules affected, similar to the previous entries.

Suggestion:

* (store/cachemulti, store/cachekv) [#20862](https://github.com/cosmos/cosmos-sdk/pull/20862) Add `Copy()` method for `CacheMultiStore` and `cachekv.Store`.
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f82bb76 and c83e2b1.

Files selected for processing (4)
  • CHANGELOG.md (1 hunks)
  • store/cachekv/store.go (1 hunks)
  • store/cachemulti/store.go (1 hunks)
  • store/types/store.go (2 hunks)
Additional context used
Path-based instructions (4)
store/cachemulti/store.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

store/cachekv/store.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

store/types/store.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Additional comments not posted (3)
store/cachemulti/store.go (1)

130-154: LGTM!

The Copy function is correctly implemented and adheres to the Uber Golang style guide. It appropriately deep copies the db field and the cachekv stores map.

store/cachekv/store.go (1)

164-194: LGTM!

The Copy function is correctly implemented and adheres to the Uber Golang style guide. It appropriately deep copies the cache, unsortedCache, and sortedCache fields.

store/types/store.go (1)

168-169: LGTM!

The addition of the Copy function to the CacheMultiStore interface is consistent with the changes made in store/cachemulti/store.go and store/cachekv/store.go. It adheres to the Uber Golang style guide.

@yihuang
Copy link
Collaborator

yihuang commented Jul 3, 2024

The implementation is very heavy though.

Comment on lines +171 to +174
for key, val := range store.cache {
newVal := *val // Create a copy of the cValue
cacheCopy[key] = &newVal
}

Check warning

Code scanning / CodeQL

Iteration over map Warning

Iteration over map may be a possible source of non-determinism
Comment on lines +178 to +180
for key := range store.unsortedCache {
unsortedCacheCopy[key] = struct{}{}
}

Check warning

Code scanning / CodeQL

Iteration over map Warning

Iteration over map may be a possible source of non-determinism
Comment on lines +137 to +142
for key, store := range cms.stores {
store, ok := store.(*cachekv.Store)
if ok {
newStores[key] = store.Copy()
}
}

Check warning

Code scanning / CodeQL

Iteration over map Warning

Iteration over map may be a possible source of non-determinism
@GAtom22
Copy link
Contributor Author

GAtom22 commented Jul 3, 2024

The implementation is very heavy though.

@yihuang Yes, will depend mostly on the amount of entries in the cache.
Do you think there's another bottleneck besides that one?

@yihuang
Copy link
Collaborator

yihuang commented Jul 15, 2024

The implementation is very heavy though.

@yihuang Yes, will depend mostly on the amount of entries in the cache. Do you think there's another bottleneck besides that one?

nop, just the deep copy itself, it also depends on the usage, if it's called multiple times for each tx, then the cost is pretty significant, and in our EVM integration, we also need to call sth like this, that's why we did the custom CoW cache store implementation.

Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Aug 15, 2024
@github-actions github-actions bot closed this Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants