monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Re: netsync restartability [was, Re: summit photos]


From: Koen Kooi
Subject: [Monotone-devel] Re: netsync restartability [was, Re: summit photos]
Date: Fri, 16 Feb 2007 22:47:35 +0100
User-agent: Thunderbird 1.5.0.9 (Macintosh/20061207)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Keller schreef:
> Timothy Brownawell schrieb:
>> On Fri, 2007-02-16 at 06:04 +1100, Daniel Carosone wrote:
>>> On Fri, Feb 16, 2007 at 04:50:49AM +1100, Daniel Carosone wrote:
>>>> I also have one at 204.152.190.23:4692
>>> (you'll need to use your keys)
>> /me notes that multi-hundred-MB revisions make netsync's restartability
>> not work so well.
>>
>> Maybe when sending fulltexts or really large diffs, we want there to be
>> a way for the sender to ask before sending, in case the receiver might
>> already have it from an interrupted sync?
>>
> 
> I'd second the request for a "resume" functionality here. One could mark
> a certain partially downloaded file delta as "unfinished" (and does the
> same with the revision as well). Maybe partial pull will bring something
> along like this... in the end this will probably rewrite the current
> netsync code quite a bit anyways...

How about starting a bit smaller and make monotone to try a bit harder to write 
the
revisions it has already received to disk. I did a small experiment on OSX 
today:

* pull ~75 (small) revs from an overloaded server
* wait till it gets wedged at 34 revs in (server was *really* getting hammered 
at that time)
* let it sit for 15 minutes
* ctrl-c

Monotone had written only 3 (three) of the 34 revs it had received. I suspect 
some
thresshold isn't getting reached when pulling all the small csets we make to 
the OE project.

regards,

KOen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF1iZ3MkyGM64RGpERAgNrAKC1fTe48+pR2hOPQ7uGPICppyiIxwCfSxJf
kBBUwifOLL/V9bT/lz0m/yg=
=ksCF
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]