Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Execution optimisation #257

@arkpar

Description

@arkpar

Execution stack is currently suboptimal. Each call involves querying code from storage, getting runtime version, initialising wasm module, etc. A bulk of work should only be done once per code change. There should be a module between state and executor that tracks code changes and caches reusable bits for each state. If the state does not have code changed since the last state it should reuse cached data for the new state.

Related: #238

Metadata

Metadata

Assignees

Labels

I9-optimisationAn enhancement to provide better overall performance in terms of time-to-completion for a task.Z3-substantialCan be fixed by an experienced coder with a working knowledge of the codebase.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions