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

Re: svn to git, N-squared?

From
Randal L. Schwartz <merlyn@stonehenge.com>
Date
Jun 12, 2006, 16:18 UTC
Message-ID
<86irn6wdob.fsf@blue.stonehenge.com>
In-Reply-To
<Pine.LNX.4.64.0606112028010.5498@g5.osdl.org>
>>>>> "Linus" == Linus Torvalds <torvalds@osdl.org> writes:

Linus> This sounds like _exactly_ what happens if you don't repack Linus> occasionally. Expecially if you are using a filesystem without hashed Linus> filename lookup, but it's true to some degree even with that - the Linus> filesystem tends to end up spending tons of time in kernel space, Linus> trying to find a place to put new objects.

I'm using git-svn to do a similar thing with a 11K-commit history. It's now 4 days running, and yes, I'm repacking and deleting empty dirs every 200-300 commits, but I'm only up to commit 4000 or so. At this rate, I *may* finish by sometime next week. :(

However, I notice one thing that can't be good: .git/git-svn/revs has one file per revision. Yes, I'll end up with 11000 files in a single directory. Ugh.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Previous: Linus TorvaldsNext: Randal L. Schwartz
Message 7 of 9 in “svn to git, N-squared?”
  1. Jon SmirlJun 12, 2006
  2. Linus TorvaldsJun 12, 2006
  3. Jon SmirlJun 12, 2006
  4. Linus TorvaldsJun 12, 2006
  5. Yakov LernerJun 12, 2006
  6. Linus TorvaldsJun 12, 2006
  7. Randal L. SchwartzJun 12, 2006
  8. Randal L. SchwartzJun 12, 2006
  9. Eric WongJun 12, 2006

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.