From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-svn: a interesting difference in performance as compared to Tortoise SVN
Date: Wed, 18 Apr 2012 15:56:09 +1000 [thread overview]
Message-ID: <CAH3AnrrY2F9rfTTFpTuBaRQmT4jHsS=WPTNTcWZGA8Oqz_UtQg@mail.gmail.com> (raw)
I thought others might be interested in this slightly
counter-intuitive performance of git-svn as opposed to Tortoise SVN.
The SVN repo is exposed via HTTP. The current tree is about 8500 files
and consumes 300MB of disk, checked out. The git repo is 200MB. There
are around 231 commits in the history.
The initially slightly counter-intuitive aspect is that given the
current state of the repo, git-svn is 4 times faster when it pulls the
entire history than TortoiseSVN is when it checks out just the current
head. It seems that the extra network cost of the extra git-svn
retrieval is dwarfed by the local processing costs of the TortoiseSVN
client.
jon.
reply other threads:[~2012-04-18 5:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH3AnrrY2F9rfTTFpTuBaRQmT4jHsS=WPTNTcWZGA8Oqz_UtQg@mail.gmail.com' \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
/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).