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

Optimize how ReadViews are fetched #2713

Open
acerone85 opened this issue Feb 13, 2025 · 0 comments
Open

Optimize how ReadViews are fetched #2713

acerone85 opened this issue Feb 13, 2025 · 0 comments

Comments

@acerone85
Copy link
Contributor

Following #2666, the ReadViewProvider is not optimized to retrieve the view stored in the graphql request data.
We should optimize the code to retrieve the least amount of views from the DB.

(Below is a list of proposed optimizations, it will be updated in the future)

Proposed optimizations:

  • The first time we check a height in the RequiredFuelBlockHeight extension, we could retrieve it from the RequiredBlockHeightSubscriptionHandle, which will need to be adapted to keep track of the latest seen BlockHeight. This way, there is no need to fetch the database view in async_graphql extensions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant