lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Migration to git


From: Greg Chicares
Subject: Re: [lmi] Migration to git
Date: Sun, 22 May 2016 03:49:14 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0

On 2016-05-22 01:00, Greg Chicares wrote:
[...]
> # Compare to clone of Vadim's repository
> 
> /home/greg/repository[0]$du -sb final/lmi vadim/lmi
> 21394883      final/lmi
> 21585360      vadim/lmi

Compare to repacked size below...

> - Should I run 'git-gc' before pushing?

/home/greg/repository[0]$rsync -av --progress final final-repacked/
/home/greg/repository[0]$cd final-repacked/final/lmi
/home/greg/repository/final-repacked/final/lmi[0]$time git repack -a -d -f 
--depth=250 --window=250
Counting objects: 32422, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (32383/32383), done.
Writing objects: 100% (32422/32422), done.
Total 32422 (delta 26058), reused 6345 (delta 0)
git repack -a -d -f --depth=250 --window=250 103.15s user 2.67s system 674% cpu 
15.688 total
/home/greg/repository/final-repacked/final/lmi[0]$du -sb
16797404        .

https://gcc.gnu.org/ml/gcc/2007-12/msg00165.html
| So the equivalent of "git gc --aggressive" - but done *properly* - is to
| do (overnight) something like
|
|       git repack -a -d --depth=250 --window=250
...
| And here, you might well want to add the "-f" flag
...
| And then it's going to take forever and a day

I'd guess it's probably O(N^2), and our N is smaller than his.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]