FreeBSD Ports statistics

[Lele Gaifax]

John Arbash Meinel wrote:
> 2) Tailor has a memory consumption bug. When I first run tailor, it does
> a full 'cvs rlog' dump, and I assume parses that into changesets. It
> then starts operating, and consumed 1GB of RAM.
> After stopping and restarting it, it is now only consuming 120MB of RAM.
> My best guess is that it parses the rlog contents, and then leaves the
> Unicode string in RAM. But doesn't write that to the state file, because
> it doesn't need it anymore.

Uhm, this clearly shouldn't happen, I'll try to figure out why it's 
keeping the usage so high.

> 3) Tailor is fairly slow, but not terribly so. It has taken about 4hrs
> to create the first 2K revisions. (With approx 6000 file-level changes).
> 
> At this point, I'm pretty sure that all of this is 'cvs' time. Tailor
> spawns 'cvs update -d -r 1.2 filename' for *every* file content change.
> It isn't able to combine multiple updates. And since RCS uses back
> patches, to checkout an early version requires applying all backwards
> patches (Thus is O(n revisions)).
> 

Maybe you already know this: 
http://progetti.arstecnica.it/tailor/wiki/CvsRepository#WhyistailorsoslowdealingwithCVS

But what do you mean with "it isn't able to combine multiple updates"?

thank you,
bye, lele.