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

evaluate the performance change for storage accesses when accessing small vs large values #12487

Open
nagisa opened this issue Nov 20, 2024 · 0 comments

Comments

@nagisa
Copy link
Collaborator

nagisa commented Nov 20, 2024

Description

In memtries only the relatively small values are held in-line, whereas the larger ones need to be fetched from the underlying storage. There is currently no cache for these values, other than what rocksdb itself may have. So the performance characteristics between these two types of accesses may be very different.

It may make sense to have two different gas fees for these two different types of accesses, depending on how much difference there really is.

cc @akhi3030 @shreyan-gupta

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