oasisprotocol / oasisprotocol/oasis-sdk
Prefetch: avoid deserializing the transaction body twice
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
One annoying thing seems to be that we will now be deserializing the body twice, once during prefetch and again in dispatch_call. Not sure how hard it would be to avoid double deserialize, maybe as a future improvement :-)
Originally posted by @kostko in https://github.com/oasisprotocol/oasis-sdk/pull/320#discussion_r680969407
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the transaction flow through the prefetch and dispatch_call entry points named in the issue, and identify where the body is deserialized in each path. Determine whether the decoded body can be reused safely; done means the transaction body is deserialized only once without changing dispatch behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100