max-mapper / max-mapper/torrent
Resources usage
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 630
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
When downloading a file, torrent can use up to 300MB of RAM and 16% of CPU.
Is this behavior expected?
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
The issue names no files, tests, or entry points. Start by reproducing a file download through the torrent CLI and measure memory and CPU usage, then inspect the download path to determine whether the reported usage is expected. Done means documenting the expected behavior or identifying a specific, reproducible resource problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100