Reduce duplicate tracking of writes in changeset and state
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 876
- Forks
- 260
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 157
Description
Unless I am missing something, this augments the changeset with all the writes, which mostly duplicate current->state except for deletes. Is that correct? If so, and if this is done for expediency, can we have a ticket that tracks that it's possible to optimise this in the future by adding only deletes here?
Originally posted by @achamayou in https://github.com/microsoft/CCF/pull/4352#discussion_r1014198531
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
Start with the changeset and current-state handling discussed in PR #4352, focusing on how writes are tracked and how deletes differ. Determine whether retaining only deletes is a valid optimization, and document or implement the resulting change with appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100