Re: [PATCH 18/19] index-helper: autorun
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 18, 2016, 07:14 UTC
- Message-ID
- <alpine.DEB.2.20.1603180752540.4690@virtualbox>
- In-Reply-To
- <CACsJy8Dx4=igm3YVYkTDdRSxevDo2xRij9P5m7VPxkVrq3oq8Q@mail.gmail.com>
Hi Duy,
On Fri, 18 Mar 2016, Duy Nguyen wrote:
Show 8 quoted lines
> On Thu, Mar 17, 2016 at 9:43 PM, Johannes Schindelin > <Johannes.Schindelin@gmx.de> wrote: > > > I know of use cases where the index weighs 300MB, and falling back to > > reading it directly *really* hurts. > > For crying out loud, what do you store in that repo? What I have in > mind for all these works are indexes in 10MB range, or maybe 50MB max.
Welcome to the real world.
> Very unscientifically, git.git index is about 274kb and contains ~3000 > entries, so 94 bytes per entry on average.
In terms of software projects' size, git.git is but a toy. Most developers deal with vastly larger (and often messier) repositories. This is especially true outside Open Source. Even the Linux kernel's repository is *tiny* compared to real-world repositories.
I am sure that David could tell many a tale about repository/working directory size, too.
So yeah, this is the challenge: to make Git work at real-world scale (didn't we hear a lot about this at the latest Git Merge?)
Ciao, Dscho