Re: [Monotone-devel] Re: cvssync status?

[Christof Petig]

Lapo Luchini schrieb:
> Christof Petig wrote:
>>>> Is out there any "documentation" how to use it?
>>> Look into monotone.texi within the branch
> OK, I read it all. (well, I read 3.14, bit it seems to be the most of
> the change isn't it?)
> I figured most of that out with hep of "monotone help cvs_pull/push",
> but I have a doubt:
> what is the quickest way to update a cvs_pull?
> It seems to me to always do a full fetch of remote CVS, even if using
> an existing preivously imported branch... or at least it takes almost
> the same time the first time and the second. Am i Missing something?
> I tried using "--since" on the second run but I got two heads with that.

cvs_pull is the quickest way to update ... but I know exactly where the
time is spent in your case: cvs_pull does not honor monotone's tree
structure but reconstructs the full CVS history from certificates. I
have better ideas for future versions but that's simply the fault of the
current code. It should not use too much bandwidth on the other hand :-S

> Are there any other pages except this one?
> http://venge.net/monotone/wiki/CvsSyncHints
> (if they are, I didn't find them...)

No that's all (besides this mail)

> I find it a bit too slow (20 minutes to update with cvs_pull a 9 MiB
> CVSROOT available locally), but I hope to have misunderstood something
> and used it sub-optimally 0=)

No, the algorithm is not overly optimized (concerning speed) and cvs is
really badly designed when it comes to retrieve old versions
incrementally. Most of the time should be spent in the cvs server.

I optimized it towards low bandwidth usage.

> And... yes, I know I probably don't "need" full history, but I would
> really really like to live with it (in case in the future I have the
> option to abandon the CVS side, I like the monotone side to already
> have all the versions).

I understand. But sadly I know that using the full history really slows
down current cvssync.

Sigh
  Christof

signature.asc
Description: OpenPGP digital signature