# Very slow git clone

**URL:** <https://forum.openwrt.org/t/very-slow-git-clone/232552>\
**Category:** Site Feedback and Other Questions\
**Created:** [May 18, 2025, 10:55am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552 "2025-05-18T10:55:46Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrakov](https://forum.openwrt.org/user_avatar/forum.openwrt.org/patrakov/32/10555_2.png) [@patrakov](https://forum.openwrt.org/u/patrakov)\
**Post date:** [May 18, 2025, 10:55am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/1 "2025-05-18T10:55:46Z")

</div>

I am in the Philippines, on the fiber ISP named "Globe". I tried to use OpenWrt SDK today, and it failed due to network timeouts:

```plaintext
[aep@aep-haswell openwrt-sdk-24.10.1-mediatek-filogic_gcc-13.3.0_musl.Linux-x86_64]$ ./scripts/feeds update
Updating feed 'base' from 'https://git.openwrt.org/openwrt/openwrt.git;openwrt-24.10' ...
Cloning into './feeds/base'...
remote: Enumerating objects: 27561, done.
remote: Counting objects: 100% (27561/27561), done.
remote: Compressing objects: 100% (12838/12838), done.
error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
failed.
Updating feed 'packages' from 'https://git.openwrt.org/feed/packages.git^d8cd30f4e281d6853b3de134c4f147a807583e43' ...
Cloning into './feeds/packages'...
remote: Enumerating objects: 7349, done.
remote: Counting objects: 100% (7349/7349), done.
remote: Compressing objects: 100% (6028/6028), done.
error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
failed.
...

```

While `git` was doing its download job, the speed was oscillating between 10 KB/s and 1 MB/s, mostly staying on the low side.

I know that the server is in Germany, so quite far, and the networks between the two countries are quite lossy.

Dear infra admins: The situation can possibly be improved by switching the TCP congestion control algorithm to BBR on the servers. Could you please do it, unless it's already set up this way or there are reasons not to?

```plaintext
$ cat /etc/sysctl.d/99-bbr.conf 
net.ipv4.tcp_congestion_control=bbr

```

Here is my old blog post regarding this optimization: [https://patrakov.blogspot.com/2018/02/a-case-of-network-throughput.html](https://patrakov.blogspot.com/2018/02/a-case-of-network-throughput.html)

---

<div class="post-metadata">

**Author:** ![anon63541380](https://forum.openwrt.org/letter_avatar/anon63541380/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon63541380](https://forum.openwrt.org/u/anon63541380)\
**Post date:** [May 18, 2025, 1:24pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/2 "2025-05-18T13:24:32Z")

</div>

Heh, but that would not close open connection...

---

<div class="post-metadata">

**Author:** ![patrakov](https://forum.openwrt.org/user_avatar/forum.openwrt.org/patrakov/32/10555_2.png) [@patrakov](https://forum.openwrt.org/u/patrakov)\
**Post date:** [May 18, 2025, 3:30pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/3 "2025-05-18T15:30:51Z")

</div>

Current non-event-based HTTP servers enforce a minimum transfer speed in order to mitigate the Slow Loris attack. So "a few seconds with zero bytes transferred" would be a good reason to close the connection server-side abruptly.

Besides, the complaint here is that, before the close, the connection struggled to keep even 10 KB/s transferred.

Although, on a second thought, the observed behavior is also consistent with a memory overuse by something else running on the same server + OOM.

---

<div class="post-metadata">

**Author:** ![anon63541380](https://forum.openwrt.org/letter_avatar/anon63541380/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon63541380](https://forum.openwrt.org/u/anon63541380)\
**Post date:** [May 18, 2025, 4:12pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/4 "2025-05-18T16:12:55Z")

</div>

Try `git config core.compression 1` might jump over timeouts or server load (not involved with project's servers, just a blind guess from symptoms)

---

<div class="post-metadata">

**Author:** ![sfx2000](https://forum.openwrt.org/user_avatar/forum.openwrt.org/sfx2000/32/10553_2.png) [@sfx2000](https://forum.openwrt.org/u/sfx2000)\
**Post date:** [May 19, 2025, 2:16am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/5 "2025-05-19T02:16:51Z")

</div>

> [@patrakov](#):
>
> Dear infra admins: The situation can possibly be improved by switching the TCP congestion control algorithm to BBR on the servers. Could you please do it, unless it's already set up this way or there are reasons not to?

Probably won't help...

BBR can be single ended, so enabling on your end also works...

---

<div class="post-metadata">

**Author:** ![patrakov](https://forum.openwrt.org/user_avatar/forum.openwrt.org/patrakov/32/10555_2.png) [@patrakov](https://forum.openwrt.org/u/patrakov)\
**Post date:** [May 19, 2025, 2:18am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/6 "2025-05-19T02:18:29Z")

</div>

According to Google presentations of that time, it needs to be enabled on the sender size.

---

<div class="post-metadata">

**Author:** ![sfx2000](https://forum.openwrt.org/user_avatar/forum.openwrt.org/sfx2000/32/10553_2.png) [@sfx2000](https://forum.openwrt.org/u/sfx2000)\
**Post date:** [May 19, 2025, 2:28am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/7 "2025-05-19T02:28:09Z")

</div>

BBR won't solve the problem...

This is more of a CDN issue - there's options here I suppose...

---

<div class="post-metadata">

**Author:** ![maxwell](https://forum.openwrt.org/letter_avatar/maxwell/32/5_5575768a8748004e209b776fc1b2916d.png) [@maxwell](https://forum.openwrt.org/u/maxwell)\
**Post date:** [July 27, 2025, 7:38pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/8 "2025-07-27T19:38:01Z")

</div>

If this git service has no defined service goals, whoever runs that server should start with doing that. If the person running that server doesn't want to do it, someone else with an interest should become the new administrator.

Onze that is resolved, one could include access from such countries as a goal oe a non-goal.

If it's considered a goal, then it could be resolved. Given the lack of response of anyone identifying as the administrator, it suggests nobody is there.

It seems like a reasonable request to me.  
Having said that, if there is a huge demand, you could always find other users willing to setup e.g. a cached server in China at a cloud company. That way you can solve the problem without depending on anyone from OpenWrt.

---

<div class="post-metadata">

**Author:** ![slh](https://forum.openwrt.org/user_avatar/forum.openwrt.org/slh/32/113591_2.png) [@slh](https://forum.openwrt.org/u/slh)\
**Post date:** [July 27, 2025, 7:41pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/9 "2025-07-27T19:41:58Z")

</div>

Sounds cool, will you foot the bill?

---

<div class="post-metadata">

**Author:** ![maxwell](https://forum.openwrt.org/letter_avatar/maxwell/32/5_5575768a8748004e209b776fc1b2916d.png) [@maxwell](https://forum.openwrt.org/u/maxwell)\
**Post date:** [July 27, 2025, 7:45pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/10 "2025-07-27T19:45:55Z")

</div>

For what should I foot the bill? I identified various steps. The first parts are entirely political in nature. If nobody in control of the [OpenWrt.org](http://OpenWrt.org) domain wants anything, then it's obvious that OP needs to find other solutions.

A bill only comes in play once there is an implemented solution, unless you meant that even designing a proper server configuration comes with a bill.

I don't live in Unconnectia.

---

<div class="post-metadata">

**Author:** ![maxwell](https://forum.openwrt.org/letter_avatar/maxwell/32/5_5575768a8748004e209b776fc1b2916d.png) [@maxwell](https://forum.openwrt.org/u/maxwell)\
**Post date:** [July 27, 2025, 8:14pm UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/12 "2025-07-27T20:14:41Z")

</div>

AI nonsense? I can assure you no AI was involved. Please stop the insults.

Also, _I_ don't have any problem. I am just trying to see whether there's an administrator anywhere to help OP.

---

<div class="post-metadata">

**Author:** ![sfx2000](https://forum.openwrt.org/user_avatar/forum.openwrt.org/sfx2000/32/10553_2.png) [@sfx2000](https://forum.openwrt.org/u/sfx2000)\
**Post date:** [July 28, 2025, 1:05am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/13 "2025-07-28T01:05:13Z")

</div>

Couple of things...

1. use the github mirror to clone against...

git clone [https://github.com/openwrt/openwrt.git](https://github.com/openwrt/openwrt.git)

1. this is for the maintainers - feeds still pull against [git.openwrt.org](http://git.openwrt.org), so the feeds are not mirrored...

Not sure who to reach out to about the feeds thing, but if this can be addressed, this should sort out most of the concerns regarding slow updates/clones...

Regarding AI - one of the scourges of the Web Space at the moment is all of the AI companies grabbing anything and everything they can to train their models, and they really don't honor the robots.txt files - I had a small family site to host private conversations, and I've had to take it offline due to this kind of activity...

---

<div class="post-metadata">

**Author:** ![RadioOperator](https://forum.openwrt.org/user_avatar/forum.openwrt.org/radiooperator/32/45876_2.png) [@RadioOperator](https://forum.openwrt.org/u/RadioOperator)\
**Post date:** [July 28, 2025, 2:09am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/14 "2025-07-28T02:09:15Z")

</div>

> [@Https://git.openwrt.org/......website speed too slow](https://forum.openwrt.org/t/https-git-openwrt-org-website-speed-too-slow/200305/7):
>
> I have to manually switch to github, as: clone from github: git clone https://github.com/openwrt/openwrt.git mod file feeds.conf.default to github: src-git packages https://github.com/openwrt/packages.git src-git luci https://github.com/openwrt/luci.git src-git routing https://github.com/openwrt/routing.git src-git telephony https://github.com/openwrt/telephony.git #src-git video https://github.com/openwrt/video.git #src-git targets https://github.com/openwrt/targets.git #src-git oldpackag…

---

<div class="post-metadata">

**Author:** ![patrakov](https://forum.openwrt.org/user_avatar/forum.openwrt.org/patrakov/32/10555_2.png) [@patrakov](https://forum.openwrt.org/u/patrakov)\
**Post date:** [July 28, 2025, 7:46am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/15 "2025-07-28T07:46:02Z")

</div>

I believe this issue will disappear soon:

> **[Future of git.openwrt.org \[Was: Re: Moving git.openwrt.org behind Fastly CDN\]](https://lists.openwrt.org/pipermail/openwrt-devel/2025-July/044174.html)**

---

<div class="post-metadata">

**Author:** ![glxwrt](https://forum.openwrt.org/user_avatar/forum.openwrt.org/glxwrt/32/86125_2.png) [@glxwrt](https://forum.openwrt.org/u/glxwrt)\
**Post date:** [September 5, 2025, 6:54am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/16 "2025-09-05T06:54:02Z")

</div>

Then [https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem](https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem) (and anywhere else `git.openwrt.org` is specified) should be updated to instead specify Github.

This has been a problem for over half a decade: [Clone git.openwrt.org slow](https://forum.openwrt.org/t/clone-git-openwrt-org-slow/42054)

Fortunately it looks like one can now log into the docs wiki with Github, we will see if I can fix it: 🤞

Edit: fixed. Whoever made it possible to edit the docs with a Github account has truly benefited humanity. I will now fix problems wherever I notice them.

---

<div class="post-metadata">

**Author:** ![maxwell](https://forum.openwrt.org/letter_avatar/maxwell/32/5_5575768a8748004e209b776fc1b2916d.png) [@maxwell](https://forum.openwrt.org/u/maxwell)\
**Post date:** [September 24, 2025, 11:28am UTC](https://forum.openwrt.org/t/very-slow-git-clone/232552/17 "2025-09-24T11:28:43Z")

</div>

This is a bad solution, because there's nothing stopping [GitHub.com](http://GitHub.com) from hosting something entirely different from the original domain, AFAIK.

So, whoever is responsible for this, clearly doesn't know what they are doing, which in turn raises the question as to why they take on the responsibility for something they can't.

I will also note that no actual problem solving has happened.
