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(x/accounts): Add schema caching feature and corresponding test case #20055
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Hwangjae Lee <meetrick@gmail.com>
Warning Rate Limit Exceeded@meetrick has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 16 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe repository updates primarily focus on enhancing GitHub workflows by adding concurrency settings and branch filtering, updating dependencies in workflow files, and refining the Changes
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
This commit modifies the queryServer struct methods to avoid copying the entire struct by adding a mutex lock. Instead of changing the receiver to a pointer, a mutex named 'mu' is introduced to synchronize access to the struct's fields. This approach minimizes the impact on other functions while ensuring safe concurrent access to the methods. Signed-off-by: Hwangjae Lee <meetrick@gmail.com>
Signed-off-by: Hwangjae Lee <meetrick@gmail.com>
@tac0turtle Hi, Could you add another reviewer as an assignee? It seems like @testinginprod hasn't been able to review since last week. |
x/accounts/query_server.go
Outdated
return schema, nil | ||
} | ||
|
||
// If not cached, generate and cache the schema |
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.
I have not much context of it, but seems like it is not a good solution, why not initialize schemas
in the constructor NewQueryServer
?
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-develope Thanks for the review. I wanted to make as few changes to the code as possible, but ended up with some ambiguous code. Following your advice to improve the code, there were many modifications. Could you review it again?
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.
hmm, I think we need more research of it, leave the decision to @testinginprod
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.
Thanks for your opinion!
- Updated all methods of the queryServer struct to use pointer receivers, ensuring compliance with the v1.QueryServer interface. - Refactored the NewQueryServer function to precalculate and store schemas for efficient schema retrieval. - Initialized the schemaCache with a precomputed length based on the length of precalculated schemas, ensuring efficient memory usage. - Added a schemas field to the queryServer struct to store precalculated schemas. - Updated the AccountQuery and Schema methods to use pointer receivers. - Added comments to describe the purpose of the Schema method. - Ensured the AccountType and AccountNumber methods use pointer receivers. Signed-off-by: Hwangjae Lee <meetrick@gmail.com>
Would it be possible not to use a mutex? I don't think this is something we'd like to have here |
func NewQueryServer(k Keeper) v1.QueryServer { | ||
return &queryServer{k} | ||
// Pre-calculate schemas for efficient retrieval. | ||
schemas := v1.MakeAccountsSchemas(k.accounts) |
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.
Since schemas are already pre-calculated here, there's no need for a mutex, nor a schemaCache.
schemas
is already 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.
Oh, nice to see you! You finally gave your opinion. Unnecessary code has sprung up as I've been modifying the code. Thanks for the review.
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.
@testinginprod Could you code review again? I updated PR by your opinion
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…osmos#20115) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: guoguangwu <guoguangwug@gmail.com>
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Marko <marko@baricevic.me>
…smos#20165) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
….5.0 (cosmos#20164) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: cuithon <dscs@outlook.com>
Signed-off-by: Hwangjae Lee <meetrick@gmail.com>
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.
Actionable comments posted: 1
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@julienrbrt I removed it, Thanks |
Description
Add schema caching feature and corresponding test case
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...
!
in the type prefix if API or client breaking changeCHANGELOG.md
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.
I have...
Summary by CodeRabbit
New Features
Enhancements
Documentation
Refactor
Bug Fixes
Chores