[Kde-scm-interest] kdelibs official branches import finished

[Thiago Macieira]

Johannes Sixt wrote:
>> For comparison: the --depth=1 clone of that KDE/kdelibs repository is
>> 12.50 MB for "master" only but 85.96 MB for all branches. That one
>> hogged the CPU for 30% and consumed 17% of its RAM (that was a 1 GB
>> machine).
>
>Uh, that's tough. I assume this was on the client side. If this is on
> the server side, this workflow won't fly.

I meant 30 seconds generating the pack, on the server side. CPU at 100%, 
17% of the RAM used.

The same machine had had problems with git before -- I've seen it try to 
use more than 500 MB of RAM (git-pack-objects), which hogs the entire 
server.

>> So we want definitely to have a repository per major branch. I'm not
>> sure about slashing history.
>
>Do you mean independent histories by "repository per major branch"?

No. I meant one common history, but not having all branches in the same 
repository. That way, one can decide what to clone.

Not that you can't do it with a single repository. But since the first 
instruction newbies get is clone (as opposed to init + remote add + edit 
configuration to fetch only a few branches, plus the fact that you cannot 
do a shallow fetch -- that's implemented only for clone).

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20071228/932dd3bf/attachment.pgp