clone / fetch operations are extremely slow on gitlab cloud repos
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
Reproduces on pygit2 1.17.0/1.18.0 / python 3.11 on Mac / Linux:
import pygit2
pygit2.clone_repository("https://gitlab.com/antora/antora", "/tmp/antora")
Takes more than 10 minutes, while the cli equivalent:
git clone https://gitlab.com/antora/antora /tmp/antora
Takes a few seconds.
Started happening ~10 days ago in our production env, worked well before and still works well for github and bitbucket hosted repos (moving the problematic repos to github solves it).
Started happening out of no where - we didn't deploy or made any change in our environment.
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 with the pygit2.clone_repository call shown in the report and compare its behavior with the git CLI for the GitLab repository. Reproduce on pygit2 1.17.0 and 1.18.0 with Python 3.11, then investigate why GitLab clones are slow while GitHub and Bitbucket clones are not. Done means clone and fetch complete in a time comparable to the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, gitlab, python
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100