Why Bitbucket used explicit core.packedgitlimit = 256m?

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

	repositoryformatversion = 0
	filemode = true
	bare = true
	packedgitlimit = 256m
	packedgitwindowsize = 32m
	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

0 votes
Adam Ahmed Atlassian Team Nov 13, 2016

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 Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

843 views 5 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