downloading metadata from pull-through cache is slow
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
0.5.0
Describe the bug
When building a project with bundler, the metadata download step is significantly slower than when using rubygems.org directly as the source.
I believe this is because Pulp does not cache metadata. Maybe we could redirect users directly to the remote's URL for metadata?
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 tracing how pull-through cache metadata is handled during a Bundler build, then compare that path with direct access to rubygems.org. Determine whether the slowdown comes from missing metadata caching or the proposed redirect behavior; done means metadata downloads are no longer significantly slower than the direct source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100