top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Git is consuming very much RAM

+1 vote
216 views

I have got a problem with my bare repository with the size of 4 GB.

I experience some strange memory usage at cloning or fetching. Git consumes about 30 GB RAM for these commands, but this is not the real problem. The real problem takes place at the client, while cloning and before the checkout. The RAM usage of GIT on the client raises also high, but too much for my machine (8 GB RAM).

What possibilities do I have to reduce this memory usage? And how do I detect what is causing this huge memory usage?

I already tested to reduce the history to the last 3 years and I also tried the BFG Repo-Cleaner, but unfortunately nothing really helps at this problem or I made a mistake during these steps.

posted Jul 15, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

How large is the software when you check it out? Do you know why the repository takes 4 GB?

answer Jul 15, 2013 by anonymous
I dont know exactly.

The history goes back to 15 years and the biggest files are some sql dumps (around 20-25 MB).

Similar Questions
0 votes

I have a problem with an already committed file into my repo. This git repo was converted from svn to git some years ago. Last week I have change some lines in a file and I saw in the diff that it is marked as binary (it's a simple .cpp file). I think on the first commit it was detected as an utf-16 file (on windows). But no matter what I do I can't get it back to a "normal text" text file (git does not detect that), but I is now only utf-8. I also replace the whole content of the file with just 'a' and git say it's binary.

Is the only way to get it back to text-mode?:
* copy a utf-8 version of the original file
* delete the file
* make a commit
* add the old file as a new one

I think that will work but it will also break my history.

Is there a better way to get these behavior without losing history?

...