Investigate copy-on-write
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
Opening this issue for a self-reminder, but if anyone is interested in having a look, please free to do it !
I'd like to investigate the performance improvement of copy-on-write.
There is a few codepaths in Bundler that copy a directory from a cache, to paste it into the working directory where BUNDLE_PATH points. For systems that supports copy-on-write, this may improve performance.
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 by locating the Bundler codepaths that copy directories from the cache into the working directory selected by BUNDLE_PATH. Investigate which supported systems provide copy-on-write and measure whether those paths benefit. Done means the performance impact and a concrete implementation scope are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100