unnecessary disk I/O
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
While copying huge data to /keybase or read it from there, the size of .local/share/keybase/ directory grows proportionally.
Why is that? It seems like bad design, because all the transfers should be between the local process and network, if the data is not synced on the device! Isn't it?
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
No file, test, or entry point is identified in the report. Start by reproducing a large copy to and from /keybase while monitoring .local/share/keybase/ growth, then trace which component performs the writes and document the expected and observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100