My team is considerign leaving our existing source control host for BitBucket, but we are a little concerned about how well BitBucket will work with our repository.
Our repository has 17.1k changesets and according to BitBucket's overview page the repository is 408.3 MB.
My concern is that the web UI appears to be taking much longer to show any pages for this large repository (5s+ to show the overview page and 6s+ to show the commit history) than it usually does for the small repositories I've used with it in the past (usually pages are nearly instant with these smaller repos). Is this normal behavior for large repositories, or can I expect this to get better as Bitbucket improves indexes on my repository, etc?
We don't impose a repo quota now. But generally speaking, once a repo get's near 1GB, HTTP performance usually takes the hit so you might want to explore using SSH either now or down the road.
That is assuming its not possible to reduce its size any? Ideally, you should keep your repo size to 100MB or less.
More on that here:
Hope this helps!
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot