Pull code from Bitbucket is very slow. How to know if Bitbucket limit access from the server or not?

[Dao Mai]

I use Git to pull code to my server. It was working normally until one day, I push a huge log file (~3GB) to Bitbucket by mistake. After that, every time I pull code from Bitbucket, it takes a long time to get response from Bitbucket (~5-10 minutes). I still pull and push code to Bitbucket normally on my computer. I don't know if Bitbucket has delay the requests from my server or not. And I'm not sure if I change the server's IP, it could solved the problem or not.

Are there any one got that problem before?

Please give me some advises, I'm very grateful for that. Thanks!

[T. Klingenberg]

If the log file was added by accident,  I can also suggest to use the BFG to remove it from the repository and reset the repository distribution to the cleaned version.

This is technically not answering you're asking for, but regardless of where at all you're hosting your git repositories you should most likely benefit from removing such large objects from VCS. It needs a little planning as you need to inform everybody involved with that repository that history was changed to keep the workflow non-interrupted.

[Dao Mai]

Thanks for your answer but the log file was not successfully added to Bitbucket server. I have also deleted the source code from server and clone new source code again without the log file in it. The problem now is every time I pull code from my server, it takes very long time to complete (5-10 minutes) so I think Bitbucket has limited access from my server IP (I'm not sure about that, just guess). I'm still pulling and pushing code normally from my local computer to Bitbucket (just take few seconds to complete). It is also happening for other projects.

[root@server public_html]# time git pull
Password:
Already up-to-date.

real    3m15.568s
user    0m0.171s
sys     0m0.184s

[T. Klingenberg]

Well, I'm not perfectly sure about that, however I could imagine that it's less the code but which historical information was transferred. So to effectively delete the file(s), all their history has to be wiped out. That's why I suggested the BFG of which I'm also not sure based on your last comment whether you've applied it or not.

In any case regarding your assumption of the network traffic with the Bitbucket Cloud and the IP address you're using I'm not qualified to comment anything on, so hopefully somebody who could might be able to leave some more feedback.

[Dao Mai]

Anyway, thank you so much :)

[Scott Harwood]

Also in same situation, takes 10 minutes to setup build, 30 seconds to run tests. I don't get it, I would have thought the docker images were cached!?