Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Why Bitbucket used explicit core.packedgitlimit = 256m?

Alexey_Efimov
Alexey_Efimov
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
November 13, 2016

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

Answer
Watch
Like Be the first to like this
783 views

1 answer

0 votes
Adam
Adam
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 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).

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events