Re: [PATCH] RFC: git lazy clone proof-of-concept
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 14, 2008, 23:38 UTC
- Message-ID
- <alpine.LSU.1.00.0802142334480.30505@racer.site>
- In-Reply-To
- <200802142300.01615.jnareb@gmail.com>
Hi,
On Thu, 14 Feb 2008, Jakub Narebski wrote:
Show 17 quoted lines
> Johannes Schindelin wrote: > > On Thu, 14 Feb 2008, Jakub Narebski wrote: > > >> Perhaps you could try running contrib/stats/packinfo.pl on this pack > >> to examine it to get to know what takes most space. > > > > $ ~/git/contrib/stats/packinfo.pl < \ > > objects/pack/pack-e4dc6da0a10888ec4345490575efc587b7523b45.pack 2>&1 | \ > > tee packinfo.txt > > Illegal division by zero at /home/imaging/git/contrib/stats/packinfo.pl > > line 141, <STDIN> line 6330855. > > Errr... sorry, I should have been more explicit. What I meant here is > the result of > > $ git verify-pack -v <packfile> | \ > ~/git/contrib/stats/packinfo.pl
Heh. I was too lazy to look up the usage, so I just did what I thought would make sense...
So here it goes:
$ git verify-pack -v
objects/pack/pack-e4dc6da0a10888ec4345490575efc587b7523b45.pack |
~/git/contrib/stats/packinfo.pl | tee packinfo.txt
all sizes: count 601473 total 2855826280 min 0 max 62173032 mean
4748.05 median 232 std_dev 221254.37
all path sizes: count 601473 total 2855826280 min 0 max 62173032 mean
4748.05 median 232 std_dev 221254.37
tree sizes: count 601473 total 2855826280 min 0 max 62173032 mean
4748.05 median 232 std_dev 221254.37
tree path sizes: count 601473 total 2855826280 min 0 max 62173032 mean
4748.05 median 232 std_dev 221254.37
depths: count 2477715 total 70336238 min 0 max 250 mean 28.39
median 4 std_dev 55.49Something in my gut tells me that those four repetitive lines are not meant to look like they do...
Show 9 quoted lines
> > 2.4G > > That's huuuuge tree. Compared to that 1.6G (or 1.4G) packfile doesn't > look large. > > I wonder if proper subdivision into submodules (which should encourage > better code by the way, see TAOUP), and perhaps partial checkouts > wouldn't be better solution than lazy clone. But it is nice to have long > discussed about feature, even if at RFC stage, but with some code.
I think partial checkouts are wrong. If you can work on partial checkouts, chances are that what you work on should be a submodule.
Having said that, I can understand if some people do not want to have the hassle of test^H^H^H^Husing submodules...
Ciao, Dscho