Re: Fixes to parsecvs

From: Francois Romieu <romieu@fr.zoreil.com>
Date: Apr 9, 2006, 23:17 UTC
Message-ID: <20060409231754.GB13138@electric-eye.fr.zoreil.com>
In-Reply-To: <1144334896.2303.259.camel@neko.keithp.com>

Keith Packard <keithp@keithp.com> : [...]

> > How well does this work with even larger repositories?
> 
> postgresql is the largest I've run; starting with a 615M CVS repository,
> it built a 1.7G .git tree, which packed down to 125M.

As a datapoint, I gave parsecvs a try on a local CVS repository. The repository weights 3.28 Go. It contains 53k files (45k non-attic).

.git/objets grew from ~100k files at the end of the first pass to 199k files (~11k commit). It took 18h on a 3GHz PIV with 2Go RAM. After 6 hours, 400 Mo were pushed to swap and parsecvs took 1.95 Go of RAM for itself. No significant swap activity. Swap grew to 900 Mo at end of run. A tarball (5 Mo) containing vmstat + size of objects is available at http://www.cogenit.fr/linux/misc/cvsparse-debug.tar.bz2

I have interrupted 'git repack -a -d' after 6 hours.

-- 
Ueimor