Why Bitbucket used explicit core.packedgitlimit = 256m?

Why follow values are default for repositories on Server with 64bit arch and 128GB of RAM?

[core]
	repositoryformatversion = 0
	filemode = true
	bare = true
	packedgitlimit = 256m
	packedgitwindowsize = 32m
[http]
	receivepack = true
[gc "stash-refs/pull-requests/*"]
	reflogExpire = never
	reflogExpireUnreachable = never

For packedGitLimit its default value on 32-bit system and 8Gb is default on 64-bit systems. Soo it look like misconfiguration...

1 answer

I don't know the answer here so I'm just commenting, but https://answers.atlassian.com/questions/239205 might be helpful. To paraphrase, this is just our standard configuration (it's hardcoded for every repo, afaict) because it seems to avoid issues across our supported platforms (apparently the 64-bit default caused issues on OSX in some cases).

Suggest an answer

Log in or Join to answer
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...

656 views 0 4
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot