Why are git operations on forked repos so much slower? Edited

Background:

My company has a self-hosted Bitbucket setup. We would like to have developers work in their own forks for added safety and to keep branches in the main repo under control. However, git operations on a forked repo are roughly an order of magnitude slower, making this a poor option.

 

Situation:

For example, I have copies of both the main repo and a synced fork on my machine. With both repos in the same state and already up to date, a simple `git fetch` takes 5 seconds on the base repo and 37-61 on the fork.

 

Question:

Why is this, and is there any way we can improve the situation?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

1,183 views 8 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you