We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently all storage operations are implemented with basic get/set operations, for example fee deduction is implemented as:
amount = store.Get(key) amount -= fee store.Set(key, amount)
But with higher level primitive in store interface, and refactor the application logic into sth like this:
store.Incr(key, -fee)
the block-stm might has some opportunity to optimize this higher level primitive more parallel friendly.
The text was updated successfully, but these errors were encountered:
Do you mean like redis incr?
Sorry, something went wrong.
I mean the store interface provided to the application logic, and special handling in block-atom layer.
No branches or pull requests
Currently all storage operations are implemented with basic get/set operations, for example fee deduction is implemented as:
But with higher level primitive in store interface, and refactor the application logic into sth like this:
the block-stm might has some opportunity to optimize this higher level primitive more parallel friendly.
The text was updated successfully, but these errors were encountered: