runtimeverification / runtimeverification/kontrol
Tracing improvements
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
After discussing with @RaoulSchaffranek, we have put together the next improvements that we can do next with tracing:
- Add the current account address in the
traceItem(id cell). - Instead of storing the account's storage map, store a diff of how the current opcode's execution affects the entire storage.
- In case of performance bottlenecks due to the high number of traceItems, we can clear the
<traceData>cell after each node is cut.
Originally posted by @anvacaru in https://github.com/runtimeverification/kontrol/issues/469#issuecomment-2027361654
Contributor guide
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
The issue names the traceItem and traceData cells and the node-cutting flow, but no files or tests. Start by locating those tracing entry points and determine how account data and storage are currently recorded. Done means the three proposed improvements are implemented and their performance impact is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100