ocurrent / ocurrent/ocurrent-deployer
Deployements are too slow
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 24
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
When updating opam.ocaml.org, the majority of the time (~3h) is spent waiting for the docker image to be pushed, then pulled again.
Would it be possible to devise a solution that would speed up this part? 99% of the content usually stay the same so maybe only the difference could be uploaded somehow?
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 tracing the deployment path used when updating opam.ocaml.org, focusing on where the Docker image is pushed and pulled. Measure those stages and investigate how unchanged image content is handled. Done means a documented, working approach that materially reduces deployment time without changing the deployed content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ocaml
- Domain
- devops, infrastructure, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100