11.06.2014 04:48, Duy Nguyen пишет: > On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer <[email protected]> wrote: >> Another part: Git wasn't ready. >> The first migration attempt failed after consuming nearly 100GB of RAM! >> When it did work it took obscene amounts of time, and the result was >> unusably large (e.g. initial checkout would take 16GB RAM on the server, >> thus not allowing a few hundred devs to do checkouts the same day). >> The current state is almost usable, but it is still obscenely slow (e.g. >> initial clone taking ~10 CPU-minutes just to figure out what to do), but >> we can just throw more hardware at it. >> (10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just >> clone the friggin repository. Too awesome!) > > Since v1.9.0 we can clone from a shallow repository. We can host two > repos on the server: a full repo and a shallow one, containing history > of only last year. Most of the time spent in initial clone is to > verify the history. Shorter history would shorten that time. But you > need to try out to see how long it actually is. I'm not sure if that > 16GB includes cloning, or just plain checkout. If the latter, Git has > a problem. >
Not sure if you can commit into that shallow repo(IIRC, you can not). I thought shallow clones is more suitable for users that want some state but do not want the whole history. -- Best regards, Sergey Popov Gentoo developer Gentoo Desktop Effects project lead Gentoo Qt project lead Gentoo Proxy maintainers project lead
signature.asc
Description: OpenPGP digital signature
