1

[enter image description here]

Result of the clone:

remote: Counting objects: 100% (250/250), done.
remote: Compressing objects: 100% (215/215), done.
remote: Total 250 (delta 30), reused 250 (delta 30), pack-reused 0
Receiving objects: 100% (250/250), 3.47 MiB | **25.00 KiB/s**, done.
Resolving deltas: 100% (30/30), done.

My problem is /gitlab v15.2.5/ clone speed only Kib/s,

It was alright few weeks ago. I checked my vps RAM and CPU usage: that was normal. What should I do?

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
upz zz
  • 11
  • 2
  • 1
    Does this happen on all projects? On all PCs you clone to? Did you try rebooting gitlab server? – GChuf Feb 28 '23 at 21:28
  • 3.47gb in objects smells like a binary that should not be included in your repo. – Kit Mar 01 '23 at 01:00

1 Answers1

0

As a workaround, consider a shallow clone, just to test if you can get an initial clone faster (with a lower depth).

But consider also, once you have finally cloned the full repository, identifying the largest commits in your repository Git history. Making sure you have trimmed the biggest file could help speed up the initial clone.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Also see if you’ve checked in a huge binary, perhaps by accident by not ignoring something that’s a build output. You can do this by examining file sizes in your local repo. – Kit Mar 01 '23 at 00:58
  • @Kit True. That is what [the link](https://stackoverflow.com/q/10622179/6309) I mention in the answer is for ("examining file sizes in your local repo") – VonC Mar 01 '23 at 07:17