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

optimizations for db_read and db_write #1781

Open
scf0220 opened this issue Jul 18, 2023 · 0 comments
Open

optimizations for db_read and db_write #1781

scf0220 opened this issue Jul 18, 2023 · 0 comments
Labels

Comments

@scf0220
Copy link

scf0220 commented Jul 18, 2023

We made some performance optimizations for db_read and db_write

  1. Provide a faster serialization method: the current method is too slow, and frequent serialization and deserialization will affect performance . pr : add fast serde for basic type  #1772
  2. Optimize gas processing: the current logic, every time you get gas, the first step is to get the store first, and the second step is to get the value from the store, we can optimize the first step . pr:optimize process gas #1771
  3. Optimize db_write performance: The current logic is that each time a set has to be written to the store, we can use the cache to record the current value, and then update the store after the transaction is executed . pr:add state cache for read/write/remove #1770
  4. Optimize the db_read function: the value acquired by the current logic needs to re-apply for a space. The current logic is to reuse the space where the value is located to avoid applying for memory space multiple times pr:add state cache for read/write/remove #1770
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants