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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,872 views 1 5
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