n0-computer / n0-computer/sendme
when receiving a large file, "exporting" takes significant additional time (few minutes)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Issue
when receiving a ~4G file there was a an "export " stage at receiving side that took multiple minutes, after the sender finished the transaction on their side
Possible cause
@matheus23 pointed out that sendme uses ExportMode::Copy from iroh-blobs, instead of other existing option, ExportMode::TryReference.
https://docs.rs/iroh-blobs/latest/iroh_blobs/api/blobs/enum.ExportMode.html
This leads to file being copied from "internal store" to target location (instead of being moved).
To confirm, I measured that on receiving file system copying the 4G file took around 7.5 minutes, which matches the previously observed delay.
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
Start by locating sendme's receiving and export path, then inspect how it selects iroh-blobs' ExportMode. Compare the current Copy behavior with the documented TryReference option and test receiving a large file; done means the unnecessary post-transfer copy is avoided without breaking export behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100