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 performance and correctness for the state in the reusable services integration #9264

Open
Tracked by #8828
IvanKavaldzhiev opened this issue Sep 3, 2024 · 4 comments
Labels
enhancement Type: New feature web3 Area: Web3 API

Comments

@IvanKavaldzhiev
Copy link
Contributor

IvanKavaldzhiev commented Sep 3, 2024

Problem

Make sure we don't have cross-contamination of State between different concurrent transactions.

We also should make sure we create a single instance bean of the other state related components - NetworkInfo, ServiceMigrator, ServicesRegistry.

Make sure the new database accessors have cache on the repository layer and the settings defined work correctly.

Solution

Validate the mentioned ideas for improvement.

If possible, opt to delete the ContractCallContext and make sure each transaction has its own set of components for proper execution.

Alternatives

No response

@bilyana-gospodinova
Copy link
Contributor

#9527 (comment) - the comment here suggest some additional optimizations related to the way accounts are being searched by

@steven-sheehy
Copy link
Member

Another optimization suggestion: #9502 (comment)

@steven-sheehy steven-sheehy moved this from 📋 Backlog to 🏃‍♀ Sprint backlog in Mirror Node Nov 10, 2024
@bilyana-gospodinova
Copy link
Contributor

A suggestion about the schemas - #9793 (comment)

@bilyana-gospodinova
Copy link
Contributor

Caching optimization - #9799 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Type: New feature web3 Area: Web3 API
Projects
Status: 🏃‍♀ Sprint backlog
Development

No branches or pull requests

3 participants