Issue #4630 invalid

cloning of large remote repositories fails due to timeout

Berkey Michaels
created an issue

Hi, I have been trying to clone git:// (large repository) via "Repositories" / Import repository

However, bitbucket always times out (cloning at gitorious or github works however), sometimes a proper error report is sent (but usually not).

While the website says that repository size is not limited by default, there is obviously a hard limit due to cloning timeout, as can be seen here?

It would be great if you could scale the timeout according to the repository size, and simply renice the background process, so that large clones are handled properly, but at a lower priority (CPU/BANDWIDTH-wise).


Comments (13)

  1. Berkey Michaels reporter

    Like I said, it's a huge repository, the repository itself is ~ 5-6 gb - and it does take a while to clone, even on a dedicated server with a 100MBIT connection.

    That said, gitorious and github seem to be able to deal with it - in fact, there are dozens of clones of this repository.


  2. Marcus Bertrand staff

    For a repository that large, I would recommend using SSH. But it is also worth noting that any repo over 1GB may have issues using Git/Mercurial with any service. If you'd like more specific information about how you can reduce the size of your repository or remove old binaries, please send a request to and we'll give you more specific detailed information.

  3. Berkey Michaels reporter

    I am not sure if the status should be changed to INVALID: Yes, it's a large repository, but there are much larger repositories used with git.

    This is not about requiring information on reducing the size of the repository: It's not my repository, it's out of my control - and other services like github and gitorious manage the size quite well, including some repositories even much larger than this.

    If you persist on keeping this INVALID, you should definitely mention these restrictions on your website, i.e. in your FAQs. Just suggesting that this is a git-specific problem is not helping, and doesn't address the fact that other git-hosting services manage hosting such repositories quite well.

  4. Julien Leloup

    Same thing here, from a push perspective : a newly created project from the Unreal Engine 4 weights nearly 1.6 GB. It cannot be pushed due to this timeout restriction.

    Is there any plan to change this timeout ? Or to allow users to modify it within a reasonnable range ?

  5. Matt Sanders

    I have never had problem with my small line of business type applications, but have now been playing with Unity3d and the repo size is much bigger. I have not been able to download the repo I pushed up onto my laptop.

  6. Alan Agon

    Similar sort of issue as the others here. We can't clone our repo at all without the remote hanging up. I've changed the default buffer to no avail.

  7. Log in to comment