[darcs-users] darcs record and huge patches

Aggelos Economopoulos aoiko at cc.ece.ntua.gr
Wed Jan 28 16:04:35 UTC 2004

On 28 Jan 2004 09:30:22 +0100
Ketil Malde <ketil at ii.uib.no> wrote:

> Aggelos Economopoulos <aoiko at cc.ece.ntua.gr> writes:
> >> So, has anyone tried running record on a large tree with many local
> >> changes? If it isn't supposed to work I'll just kill the process,
> >but> if is, how long should it take?
> > Well, it took about five hours, but seems to have worked (produced a
> > 27M patch (6M compressed)). Still, it doesn't seem normal that it
> > should take that long or consume so much memory - can't you force
> > garbage collection at some point? Would disabling use of mmap() help
> > in such extreme cases?
> If you have a self-compiled darcs, you could try to recompile it with
> profiling (add "-prof" to the compiler switchesΉ). If you then run the
> same command with the additional parameters "+RTS -p -RTS", which will
> give you a breakdown of time usage per function.

Next rainy afternoon I'll give it a shot ;)


More information about the darcs-users mailing list