why is hg pull so slow?

When I hg clone my bitbucket repo it takes 40 minutes. When I hg pull my repo it can take 20-30 minutes even if not much has changed. My .hg folder is about 200MB.

Can anyone help me troubleshooting this? I get similar performance whether I am on the corporate connection or my home ADSL2+ connection.

2 answers

1 accepted

My experience with Mercurial in particular is that adding large binaries to the repo results in a huge memory footprint whenever they are operated on, slowing the works down to a crawl.

If your changesets are very large, or otherwise contain large binaries, I would highly advise switching to GIT instead, which doesn't have such problems.

I'd go with GIT also. It works a lot better.

Hi Jerry,

Note that DVCS soultions are designed to handle few amounts of data, so large binaries (we don't recommend binaries on DVCS) and hundreds of MB will naturaly takes some time to sync. I believe that Git (also supported on Bitbucket) is little bit faster, so maybe you can try it to solve this issue.



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
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...

2,049 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