1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #7251 invalid

very slow git pull (but not push) speeds only with bitbucket

Scott Sells
created an issue

I just recently started using bitbucket and am having an issue with very slow download speeds with git pull. Downloads of files through the web interface (from a repo's downloads page) are fine.

As a test, I created a repo with about 250mb (https://bitbucket.org/scottcs/speedtest). When pushing the initial commit to bitbucket, it took only 7m6.44s. I then immediately cloned the repo to a new directory, and that took 34m32.52s. For some reason the download transfer speed tops off between 90-100 KB/s. I am experiencing this slowness on both osx and windows, both using ssh and https, and on more than one bitbucket repo.

I had about 8 other people at my company clone my speedtest repo and they all had times between 2m-8m.

I first noticed the problem when trying to clone our company's repo (which is over 1GB in size). I've tried cloning from github, as well, and that is very fast.

I'm not sure how to further troubleshoot the problem, so I'd appreciate any help. Thanks.

Comments (106)

  1. Marcus Bertrand staff

    It really depends on where you live and the network between us. We don't have any throttling for any reason and our connection is more than capable of matching your speeds.

    I'd advise trying a different network connection to compare, especially one with fewer traffic filters between us. If you want to help us track this, please report a traceroute to bitbucket support at support.atlassian.com.

  2. Michele Olivo

    Italy: My network speed is about 6-700kiB/s 0% (78/8777), 1.21 MiB | 13 KiB/s After some hours (at 10KiB/s) i have received this error git pull remote: Counting objects: 8781, done. remote: Compressing objects: 100% (6251/6251), done. Write failed: Broken pipe 73% (6439/8777), 88.23 MiB | 11 KiB/s
    fatal: The remote end hung up unexpectedly fatal: EOF prematuro fatal: recursion detected in die handler

  3. chriserwin

    Having similar issues with push, excruciatingly slow speed of 120KiB/s

    My connection is capable of 1Mb/s

    Unfortunately going to have to move to another git host, this simply won't work.

  4. Johannes Mentz

    Its the same issue for me. I currently fetch with a bandwith between 60 to 130 kb/s. Connections to other servers than bitbucket are fast. I just downloaded the Android SDK (~400 MB) in about three minutes, for example.

  5. Sami Darko

    Same thing from France : error: RPC failed; result=56, HTTP code = 200 1 KiB/s
    fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed

  6. Marcus Bertrand staff

    All, this issue remains closed. We're aware of a completely different issue affecting some users who either use or depend on France Telecom and are collecting data to contact our provider. However, we recommend that you contact your ISP first and report the issue. In nearly every case, we've found network issues between your ISP and ours (NTT/Verio) are to blame and are outside of our direct control. Contacting your ISP goes a long way for them to help and work with us to fix the issue.

  7. Marcus Bertrand staff

    If you wish to provide us data on your connection, please do so in support. Email support@bitbucket.org with at least the following:

    • Your Geographic location
    • Your ISP
    • A traceroute to bitbucket.org
    • If you can install it for your platform, use tcptraceroute to perform a better trace to bitbucket.org on port 80
  8. Harm Verhagen

    we (server in Paris) are experiencing very slow connections with bitbucket (git push and pull). At the same moment pulling/pushin github is blazingly fast.

    example of problem: it takes up to 10 seconds, when pulling/pushing over https to bitbucket, before git even asks for a password.

    We do not see this all the time, but often enough thats its annoying. We see this on our production servers too. (good connectivity)

  9. dlage

    For the ones using Putty (or any similar implementation upon Putty's plink), this can help you: Try enabling in Putty (Default Settings) the following settings:

    1. SSH -> Auth: "Allow agent forwarding" (I believe this is the one that changes "everything")
    2. SSH -> "Enable Compression"
    3. Session -> Select "Default Settings" -> Save

    For me, this resulted in going from 143.00 KiB/s to 4.50 MiB/s

    Hope this helps.

  10. Eric Murphy

    Slow speeds for me too in Florida (33 KiB/s). This is an ongoing problem. Packet loss on bitbucket.org:

    PING bitbucket.org (131.103.20.168): 56 data bytes 64 bytes from 131.103.20.168: icmp_seq=0 ttl=57 time=73.770 ms 64 bytes from 131.103.20.168: icmp_seq=1 ttl=57 time=72.744 ms Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 64 bytes from 131.103.20.168: icmp_seq=4 ttl=57 time=73.188 ms 64 bytes from 131.103.20.168: icmp_seq=5 ttl=57 time=78.039 ms 64 bytes from 131.103.20.168: icmp_seq=6 ttl=57 time=74.883 ms 64 bytes from 131.103.20.168: icmp_seq=7 ttl=57 time=75.936 ms 64 bytes from 131.103.20.168: icmp_seq=8 ttl=57 time=72.206 ms 64 bytes from 131.103.20.168: icmp_seq=9 ttl=57 time=78.043 ms 64 bytes from 131.103.20.168: icmp_seq=10 ttl=57 time=71.488 ms 64 bytes from 131.103.20.168: icmp_seq=11 ttl=57 time=71.600 ms Request timeout for icmp_seq 12 64 bytes from 131.103.20.168: icmp_seq=13 ttl=57 time=76.858 ms 64 bytes from 131.103.20.168: icmp_seq=14 ttl=57 time=72.749 ms 64 bytes from 131.103.20.168: icmp_seq=15 ttl=57 time=71.871 ms 64 bytes from 131.103.20.168: icmp_seq=16 ttl=57 time=76.233 ms 64 bytes from 131.103.20.168: icmp_seq=17 ttl=57 time=77.260 ms 64 bytes from 131.103.20.168: icmp_seq=18 ttl=57 time=74.668 ms 64 bytes from 131.103.20.168: icmp_seq=19 ttl=57 time=75.885 ms 64 bytes from 131.103.20.168: icmp_seq=20 ttl=57 time=99.887 ms 64 bytes from 131.103.20.168: icmp_seq=21 ttl=57 time=74.981 ms 64 bytes from 131.103.20.168: icmp_seq=22 ttl=57 time=72.430 ms 64 bytes from 131.103.20.168: icmp_seq=23 ttl=57 time=79.745 ms 64 bytes from 131.103.20.168: icmp_seq=24 ttl=57 time=72.772 ms 64 bytes from 131.103.20.168: icmp_seq=25 ttl=57 time=71.957 ms 64 bytes from 131.103.20.168: icmp_seq=26 ttl=57 time=73.892 ms Request timeout for icmp_seq 27 64 bytes from 131.103.20.168: icmp_seq=28 ttl=57 time=76.143 ms 64 bytes from 131.103.20.168: icmp_seq=29 ttl=57 time=74.171 ms ^C --- bitbucket.org ping statistics --- 30 packets transmitted, 26 packets received, 13.3% packet loss round-trip min/avg/max/stddev = 71.488/75.515/99.887/5.356 ms

    I did a traceroute and it did not even complete!

  11. David Dumke

    Really really slow again, when are you guys going to fix this? All the other sites seem fine and all I see in the issues are that you are setting them to invalid.

    1:  RfmLinuxDev.local                                     0.076ms pmtu 1500
     1:  gateway.ikt.uni-hannover.de                           0.634ms
     1:  gateway.ikt.uni-hannover.de                           0.596ms
     2:  130.75.73.62                                          1.115ms
     3:  bwingate.rrzn.uni-hannover.de                         1.202ms
     4:  XWINgate.rrzn.uni-hannover.de                         3.066ms
     5:  xr-han1-te1-3.x-win.dfn.de                            1.992ms
     6:  cr-han1-te0-7-0-0.x-win.dfn.de                        2.993ms
     7:  cr-fra1-hundredgige0-6-0-1-7.x-win.dfn.de             8.179ms
     8:  ae53.edge5.Frankfurt1.Level3.net                      8.927ms
     9:  ae-4-90.edge6.Frankfurt1.Level3.net                   6.964ms
    10:  xe-0-3-0-15.r02.frnkge03.de.bb.gin.ntt.net            7.634ms
    11:  ae-2.r20.frnkge04.de.bb.gin.ntt.net                   8.511ms
    12:  ae-1.r21.asbnva02.us.bb.gin.ntt.net                 105.546ms asymm 13
    13:  ae-2.r00.asbnva02.us.bb.gin.ntt.net                 104.206ms asymm 12
    14:  po-2.a00.asbnva03.us.da.verio.net                   112.376ms asymm 13
    15:  no reply
    16:  no reply
    17:  no reply
    18:  no reply
    19:  no reply
    20:  no reply
    21:  no reply
    22:  no reply
    23:  no reply
    24:  no reply
    25:  no reply
    26:  no reply
    27:  no reply
    28:  no reply
    29:  no reply
    30:  no reply
    31:  no reply
         Too many hops: pmtu 1500
         Resume: pmtu 1500
    
  12. Matt Jensen

    Also painfully slow here in Melbourne, Australia, when cloning - the files don't start coming down to my machine for 10 minutes... Once they come they come very fast though, in about 5 seconds.

  13. dale fletter

    painfully slow (<50kbps) UC Davis

    traceroute to bitbucket.org (131.103.20.168), 64 hops max, 52 byte packets 1 128.120.75.254 (128.120.75.254) 12.874 ms 12.994 ms 1.983 ms 2 adf5-1--cdf1 (128.120.10.145) 1.188 ms 1.048 ms 1.037 ms 3 ucd-cdf1--border-dav-cmp (192.82.111.66) 1.858 ms 2.358 ms 3.643 ms 4 oak-agg1-ucdavis-10ge.cenic.net (137.164.3.200) 3.846 ms 3.181 ms 3.235 ms 5 dc-svl-core1--oak-agg1-10ge.cenic.net (137.164.47.115) 5.160 ms 6.044 ms 8.026 ms 6 dc-svl-isp1--svl-core1-10ge.cenic.net (137.164.47.132) 4.571 ms 5.868 ms 6.268 ms 7 xe-4-1-2.edge1.sanjose1.level3.net (4.53.16.185) 42.862 ms 42.636 ms 43.919 ms 8 ae-1-60.edge1.sanjose3.level3.net (4.69.152.16) 70.291 ms ae-4-90.edge1.sanjose3.level3.net (4.69.152.208) 43.099 ms 41.404 ms 9 4.68.111.250 (4.68.111.250) 41.672 ms 44.848 ms 43.875 ms 10 ae-7.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.52) 44.954 ms 52.213 ms 88.702 ms 11 ae-4.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.102) 77.292 ms 78.145 ms 73.662 ms 12 ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207) 85.357 ms 75.936 ms 76.555 ms 13 * 14 * 15 * 16 * 17 * 1

  14. Hugo Dumais

    Please look into using Cygwin SSH client. I'm able to get around 13mb/sec on a 200mbps connection. Plink gave me 300kb/sec. Openssh for windows gave me 800kb/sec.

  15. Michael Ellan

    Ditto here from Philly. Its taken nearly 2 hours to clone 30% of a 1GB repo, I should have been done with the work by now but nope, still waiting... This is a joke.

  16. Chadwick

    thanks Hugo Dumais for good suggestions.

    Marcus Bertrand This is probably then not at all a bitbucket issue but an ssh/windows client issue. It is possible that there is an issue really with compatibility with putty<->bitbucket or not great compression. In any case, it is clear that switching to https or using another method than plain putty is necessary. could bitbucket please do a bit of checking into the compression / other clients? Noise on closed tickets like this usually means the common user is so affected that it's probably pretty important. Thanks

  17. pinkal vansia

    Getting 7-10 Kb/s on 2 mb/s connection in India. Tried cloning 15mb repo 10 times without success. Every time getting following error

    2014-08-05 12:26:11,965 [5795979] INFO - git4idea.commands.GitHandler - remote: Counting objects: 13329, done. 2014-08-05 13:04:40,721 [8104735] INFO - git4idea.commands.GitHandler - fatal: early EOF 2014-08-05 13:04:40,733 [8104747] INFO - git4idea.commands.GitHandler - remote: Compressing objects: 100% (6946/6946), done. 2014-08-05 13:04:40,734 [8104748] INFO - git4idea.commands.GitHandler - fatal: The remote end hung up unexpectedly 2014-08-05 13:04:40,734 [8104748] INFO - git4idea.commands.GitHandler - fatal: index-pack failed

    Don't know what to do.

  18. Shobhit Puri

    I am having the same issue very slow clone/pull etc. Earlier it was fine. Its not an issue with my ISP as for my other colleagues at the same place, its working fast. The net is pretty fast. The download speed from speedtest is more than 100Mbps.

  19. Steven Du

    traceroute to bitbucket.org (131.103.20.167), 30 hops max, 60 byte packets 1 155.69.151.254 (155.69.151.254) 0.378 ms 0.585 ms 0.586 ms 2 172.30.143.194 (172.30.143.194) 0.582 ms 0.811 ms 0.813 ms 3 155.69.1.253 (155.69.1.253) 0.688 ms 0.674 ms 0.914 ms 4 * 5 * 6 * 7 * 8 * 9 * 10 * 11 * 12 * 13 * 14 * 15 * 16 * 17 * 18 * 19 * 20 * 21 * 22 * 23 * 24 * 25 * 26 * 27 * 28 * 29 * 30 * *

    I will test a new push later

  20. Fareesh Vijayarangam

    Getting 10 KB/s pull speeds on ubuntu

    traceroute to bitbucket.com (131.103.20.173), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.263 ms 0.304 ms 0.395 ms 2 116.72.133.1 (116.72.133.1) 2.488 ms 2.434 ms 2.361 ms 3 125.99.121.13 (125.99.121.13) 3.478 ms 3.427 ms 3.499 ms 4 192.168.210.105 (192.168.210.105) 3.498 ms 3.203 ms 3.121 ms 5 * 192.168.27.2 (192.168.27.2) 3.087 ms 3.079 ms 6 125.99.99.254 (125.99.99.254) 3.163 ms 2.966 ms 2.950 ms 7 125.99.99.253 (125.99.99.253) 4.076 ms 4.076 ms 4.048 ms 8 59.162.20.241.static-mumbai.vsnl.net.in (59.162.20.241) 12.505 ms 12.505 ms 9 * 10 ge-101-0-0-42.r01.tkokhk01.hk.ce.gin.ntt.net (203.131.241.158) 97.757 ms 95.465 ms 97.691 ms 11 ge-101-0-0-42.r01.tkokhk01.hk.bb.gin.ntt.net (203.131.241.157) 95.974 ms 96.338 ms 96.599 ms 12 ae-2.r23.tkokhk01.hk.bb.gin.ntt.net (129.250.5.156) 98.740 ms ae-3.r22.tkokhk01.hk.bb.gin.ntt.net (129.250.6.232) 95.709 ms ae-2.r23.tkokhk01.hk.bb.gin.ntt.net (129.250.5.156) 93.659 ms 13 ae-12.r22.osakjp02.jp.bb.gin.ntt.net (129.250.6.234) 143.005 ms 141.698 ms 145.250 ms 14 ae-9.r20.osakjp02.jp.bb.gin.ntt.net (129.250.6.91) 141.506 ms ae-8.r20.osakjp02.jp.bb.gin.ntt.net (129.250.6.189) 140.489 ms 143.599 ms 15 ae-8.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.164) 266.788 ms 260.183 ms 258.889 ms 16 ae-9.r21.asbnva02.us.bb.gin.ntt.net (129.250.6.238) 331.684 ms * 328.412 ms 17 ae-2.r05.asbnva02.us.bb.gin.ntt.net (129.250.4.41) 320.275 ms ae-2.r06.asbnva02.us.bb.gin.ntt.net (129.250.7.27) 308.287 ms ae-2.r05.asbnva02.us.bb.gin.ntt.net (129.250.4.41) 308.916 ms 18 xe-0-8-0-19.r05.asbnva02.us.ce.gin.ntt.net (129.250.203.54) 316.475 ms 317.153 ms 328.976 ms 19 * 20 * 21 * 22 * 23 * 24 * 25 * 26 * 27 * 28 * 29 * 30 * *

  21. Martin Kalis

    Dear Marcus Bertrand, I don't understand why this issue is still in status "invalid".

    I am adding extra traceroute information. Still - our paid account gets pull quite fast, free accounts have problem and timeout in most cases.

    Traceroute via cable provider: traceroute to bitbucket.org (131.103.20.167), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 37.659 ms 11.004 ms 6.037 ms 2 192.168.1.1 (192.168.1.1) 3.609 ms 1.719 ms 2.741 ms 3 176-10-40-177.lastmile.sk (176.10.40.177) 3.761 ms 29.612 ms 12.179 ms 4 217.145.193.41 (217.145.193.41) 4.153 ms 2.297 ms 2.774 ms 5 195.28.89.250 (195.28.89.250) 12.908 ms 4.297 ms 21.021 ms 6 ge2-0-0.bratislava1.bra.seabone.net (79.140.90.8) 12.933 ms 5.080 ms 21.341 ms 7 xe-0-1-3.franco31.fra.seabone.net (89.221.34.105) 22.588 ms xe-3-1-1.franco31.fra.seabone.net (195.22.211.107) 23.252 ms 42.160 ms 8 xe-1-2-3.franco31.fra.seabone.net (195.22.214.79) 17.615 ms xe-0-0-0.franco31.fra.seabone.net (195.22.211.193) 33.912 ms xe-10-1-1.franco31.fra.seabone.net (195.22.211.205) 24.383 ms 9 ntt-verio.franco31.fra.seabone.net (195.22.214.63) 29.170 ms 35.353 ms 18.891 ms 10 ae-2.r20.frnkge04.de.bb.gin.ntt.net (129.250.5.217) 28.400 ms 28.106 ms 24.160 ms 11 ae-7.r20.asbnva02.us.bb.gin.ntt.net (129.250.3.20) 134.214 ms 109.474 ms 12 ae-1.r05.asbnva02.us.bb.gin.ntt.net (129.250.4.14) 105.056 ms 119.608 ms ae-1.r06.asbnva02.us.bb.gin.ntt.net (129.250.7.25) 102.488 ms 13 xe-0-2-0-19.r06.asbnva02.us.ce.gin.ntt.net (129.250.203.90) 102.073 ms xe-0-8-0-19.r05.asbnva02.us.ce.gin.ntt.net (129.250.203.54) 100.739 ms 101.612 ms 14 * 15 * 16 * 17 * *

    Traceroute via mobile internet (the same result): traceroute to bitbucket.org (131.103.20.168), 64 hops max, 52 byte packets 1 172.20.10.1 (172.20.10.1) 4.715 ms 4.204 ms 8.039 ms 2 10.168.126.97 (10.168.126.97) 48.379 ms 286.116 ms 118.896 ms 3 ip-160-218-1-57.eurotel.cz (160.218.1.57) 70.153 ms 44.559 ms 42.760 ms 4 194.228.190.181 (194.228.190.181) 62.524 ms 43.852 ms 47.352 ms 5 194.228.190.157 (194.228.190.157) 46.554 ms 52.414 ms 52.026 ms 6 194.228.190.193 (194.228.190.193) 52.353 ms 47.050 ms 49.159 ms 7 cesky-1-0-0-0-100-grtprach1.red.telefonica-wholesale.net (5.53.0.25) 72.119 ms * 8 xe-4-0-0-0-grtpartv2.red.telefonica-wholesale.net (94.142.121.34) 443.210 ms 477.080 ms xe0-0-0-0-grtpareq1.red.telefonica-wholesale.net (94.142.120.78) 513.528 ms 9 xe6-0-8-0-grtwaseq2.red.telefonica-wholesale.net (94.142.116.205) 815.390 ms 292.697 ms 10 xe-0-7-0-8.r06.asbnva02.us.bb.gin.ntt.net (129.250.8.93) 543.642 ms xe-0-3-0-8.r06.asbnva02.us.bb.gin.ntt.net (129.250.9.182) 325.978 ms 225.359 ms 11 xe-0-2-0-19.r06.asbnva02.us.ce.gin.ntt.net (129.250.203.90) 187.199 ms 161.864 ms 1648.114 ms 12 * 13 * 14 * 15 * 16 * * *

    Marcus Bertrand, cannot it be the problem of location of your servers? Are they hosted only in Australia/US, or also in Europe? Is there any setting according to which we can decide which server would be primary?

    Thanks

    Martin

  22. David Hudlow

    How about we re-open the issue as valid and Atlassian can solve it by using a decent hosting company (or ISP)? You guys realize that BitBucket is fundamentally a data hosting service, right? And you're gonna tell me with a straight face that I need to call Verizon and tell them that they need to figure out how to get a better connection to bitbucket.org? Come on.

    I'm in Dallas, TX on a 50/50 FIOS line and I get 100-180 KiB/s cloning. Our company recently moved from GitHub. Didn't know that a side-effect would be spotty nationwide connection speeds.

  23. nordicdyno NA

    Yeah! I approve crazy slow ssh connection with bitbucket. SSH banner message doesn't appear in seconds! (just banner!) Problem reproduces on our RU and DE servers. We are hardly thinking about migration if nothing changes

  24. Daniele Brugnara

    Since this morning I can't do pulls. It's not related on connection nor pc. I've tried on two different locations (italy and austria) with same crappy results: pull stays more than 5 minutes and does nothing. Very bad.

  25. Mauricio Leyzaola

    I am aware many Bitbucket users come here because the private repositories are free, but honestly guys, even a free product that has this HUGE problem must be resolved. This is a screenshot of what happens often at my end in Mexico and also with my data center in NY, US. So many people can't be wrong.

    Screenshot 2015-04-22 21.31.24.png

    4310230518.png

  26. Suyash Sumaroo

    Fresh connection problems! Until now, it was ok but since two days, my git push is stuck at 10.00 KiB/s seemingly forever. Any solutions apart from the usual 'contact your ISP'?

  27. Wiliam Azzam

    Atlassian products allways have been slow and when you complain they ask you to trace and profile...

    Private and paid repositories. SPAIN Internet: 200/15 Bitbucket: 90 KiB/s

  28. Quan Pham

    I have the same problem :( pushing is too slow. I sure that it's not a problem on my network. Writing objects: 27% (62/226), 9.06 MiB | 26.00 KiB/s

  29. Dan Smith

    Slow here too. ~160 KiB/s on a 152MiB/s line in Reading, England (good data links).

    I'm currently pulling from three repos and all are showing similar speeds. Adding additional downloads also run at the same speed. This shows that rate limiting is in place, despite staff claims.

  30. Tom Spencer

    After searching threads like this for a solution, the one posted by Mesar Hameed works an absolute treat. I added the following lines to ~/.ssh/config:

    Host bitbucket.org
      ControlMaster auto
      ControlPersist 2h
      ControlPath /tmp/%r@%h:%p
      ServerAliveInterval 90
    

    and after a reboot, all my bitbucket slowness has gone away!

    If you are experiencing the issues reported here, I'd encourage you to give this a try. These settings basically keep a SSH connection open to bitbucket, so after the initial session is setup (which will likely still be slow), subsequent pushes and pulls should be much quicker, since there is no overhead in creating a new SSH session (which appears to be the major cause of the slowness described here, and elsewhere).

    Some background on the ControlMaster setting: https://developer.rackspace.com/blog/speeding-up-ssh-session-creation/

  31. Mahdi Tounsi

    I'll leave the bitbucket because here's connection limit

    I'm going to Github. I can not be depending on 100KiB or 500KiB, not will have the chutzpah to say that the problem is my connection. Because I low daily all kinds of content (from 2 to 10GB, and I have no problems). Low in all forms, P2P, direct link, etc ..

    Including my GitHub repositories lower at high speed.

    FUNNY, BECAUSE IT IS ONLY IN bitbucket IS A SPEED OF CRAP!

    BYE BITBUCKET, BYE! I AM TIRED OF YOU!

  32. Log in to comment