From: Jakub Narebski <jnareb@gmail.com>
To: weigelt@metux.de
Cc: git@vger.kernel.org
Subject: Re: Incremental object transfer
Date: Sat, 13 Nov 2010 10:31:36 -0800 (PST) [thread overview]
Message-ID: <m31v6pf54h.fsf@localhost.localdomain> (raw)
In-Reply-To: <20101112103427.GA29057@nibiru.local>
Enrico Weigelt <weigelt@metux.de> writes:
> As already said some time ago, I'm using git to back up maildirs
> on a machine w/ relatively low ram. The biggest problem for now
> is the initial push (maybe later larger subsequent pushes could
> be also affected too): it takes quite a long time to get everything
> packed, and if the connection breaks (the box is sitting behind
> a dynamic-IP DSL link), everything has to be restarted :(
>
> So my idea is to incrementally transfer objects in smaller packs,
> disable gc on remote side and update refs when some commit is
> complete.
>
> Is there any way to do this ?
This would work only for "dumb" transports: "dumb" HTTP transport and
deprecated rsync transport.
"Smart" transport (e.g. git://, SSH, new "smart" HTTP transport) all
create packs to send on the fly. Those packs would rarely be
byte-for-byte the same, even if both server and client have the same
objects, unless perhaps on single code (unthreaded).
There were discussion about resumable download, by examining what got
downloaded in partial pack; but this is a hard problem.
So I would recommend either creating a bundle (see git-bundle
manpage), which can be resumably downloaded via HTTP, FTP, P2P - it is
an ordinary file. Or you can try cloning via rsync (but the
repository should be quiescent).
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-11-13 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 10:34 Incremental object transfer Enrico Weigelt
2010-11-12 16:09 ` Jonathan Nieder
2010-11-13 18:31 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31v6pf54h.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).