monotone-devel
[Top][All Lists]
Advanced

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

Re: [Monotone-devel] partial pull #3 - calling conventions


From: Christian Ohler
Subject: Re: [Monotone-devel] partial pull #3 - calling conventions
Date: Sat, 26 May 2007 17:21:25 +0200

Thomas Keller, 2007-05-25:

I'm not completly in this topic, so I might be perfectly wrong, but wouldn't it be possible to just fetch the revision_id graph and leave out revision texts, roster and file data for gap/unfetched revisions, just mark them in a special way?

Or how about simply transmitting all revisions and certs, and omitting only file contents? It seems like this should reduce the network traffic by a considerable amount while being much less complicated than approaches that omit revision data.

Currently, an initial pull from venge.net restricted to 'net.venge*' transfers around 71MB according to mtn's tickers. The following simple estimates suggest that pulling only revisions and certs should transfer around 10MB:

$ mtn automate graph |cut -d\ -f 1 |xargs -n 1 mtn automate get_revision |gzip >nvm-revisions.gz $ mtn automate graph |cut -d\ -f 1 |xargs -n 1 mtn ls certs |gzip >nvm-certs.gz
$ du -h nvm*
1.0M    nvm-certs.gz
9.2M    nvm-revisions.gz

Perhaps this would be good enough?

Christian.




reply via email to

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