git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-svn: a interesting difference in performance as compared to Tortoise SVN

From
Jon Seymour <jon.seymour@gmail.com>
Date
Apr 18, 2012, 05:56 UTC
Message-ID
<CAH3AnrrY2F9rfTTFpTuBaRQmT4jHsS=WPTNTcWZGA8Oqz_UtQg@mail.gmail.com>

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.
Message 1 of 1 in “git-svn: a interesting difference in performance as compared to Tortoise SVN”
  1. Jon SeymourApr 18, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.