So what I did was went in and updated
the /var/opt/gitlab/git-data/repositories/reponame.git/config file so it
looked like this:
[core]
repositoryformatversion = 0
filemode = true
bare = true
[pack]
windowMemory = 128m
packSizeLimit = 512m
and then repacked the repo: #git repack -a -d
I also increased the swap from 2 to 3GB but after these settings were in
effect and the repo repacked, git hardly touched the swap file.
What I would love to know however is if a file I can edit that controls
what those initial config files look like so I don't have to do this for
every new repo that is created
On Friday, November 14, 2014 2:08:20 PM UTC-5, Ryan W wrote:
>
> Right now our gitlab server is using up all of it's memory when people try
> to clone repos over 3GB in size.. I've created a 2GB swap partition but
> we're still chewing through all of that for larger repos as the packing
> process sucks up more ram than we can spare. So I wanted to check if there
> is a setting that I can configure in Gitlab or if I should install git and
> set it that way?
>
> The server instance I setup gitlab on doesn't have git installed so I am
> going to have to apt-get install git to get it up and running in order to
> set my packsizelimit. Not wanting to rock the boat I assumed that git
> wasn't installed for a reason and wanted to check if there was a gitlab
> only way that I could adjust this variable to limit the pack size to a few
> hundred MB instead.
>
> thanks!
>
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/25bd7a3b-87ea-4717-8d24-2f4c5eaa3b86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
