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

git svn's performance issue and strange pauses, and other thing

From
HLHin-Tak Leung <htl10@users.sourceforge.net>
Date
Sep 18, 2014, 07:39 UTC
Message-ID
<1411025993.80693.YahooMailBasic@web172304.mail.ir2.yahoo.com>
(I am not on the list - please CC)
Thanks for git-svn - I use it instead of subversion itself for many years now.

Just thought I'd ask/report a few issues I noticed for some time now, of tracking development of a particular subversion-based development project. Broadly speaking, I think there are 3 problems, especially noticeable against a particular repository, but to a lesser extent with some others too.

- just doing "git svn fetch --all" seems to consume a lot of memory,
for very little actual fetched changes. (in the 2GB+ region, sometimes).
- "git svn fetch --all" also seems to take a long time too, for certain
fetched changes. (in the minutes region).
-  I know I can probably just "read the source", but I'd like to know
why .git/svn/.caches is even larger than .git/objects (which supposedly
contains everything that's of interest)? I hope this can be documented
towards the end of the man-page, for example, of important parts
of .git/svn (and what not to do with them...), without needing to
'read the source'. Here is part of "du" from a couple of days ago:

254816 .git/objects 307056 .git/svn/.caches 332452 .git/svn 588064 .git

The actual .git/config is here - this should be sufficient info for somebody looking into experiencing the issues I mentioned above.

--------
$ more .git/config 
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[svn-remote "svn"]
	url = https://svn.r-project.org/R
	fetch = trunk:refs/remotes/trunk
	branches = branches/*:refs/remotes/*
	tags = tags/*:refs/remotes/tags/*
[pack]
	threads = 1
------------
Next: Eric Wong
Message 1 of 4 in “git svn's performance issue and strange pauses, and other thing”
  1. Hin-Tak LeungSep 18, 2014
  2. Eric WongSep 19, 2014
  3. Jakob Stoklund OlesenSep 19, 2014
  4. Eric WongOct 5, 2014

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.