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

[problem] out of memory

From
FHFrédéric Heulin <frederic.heulin@free.fr>
Date
Jan 27, 2010, 17:16 UTC
Message-ID
<821836537.2475221264612596403.JavaMail.root@spooler9-g27.priv.proxad.net>
Hi All,

I have a cvs repository I try to convert to git. I have used cvs2git (1 week old) to get the dumps from cvs. To be able to do the fast-import import into the new git. I had to use a bigger machine than mine (the big is 64bits, 8GB ram, mine is 32bits,4GB ram) because on my machine git ran out of memory. Once converted, I tried to do a clone, it ran out of memory on my machine.

 - version used for gitc
   - on my machine : 1.6.6.1
   - on the big machine : 1.5.6.5 (debian lenny)
 - Here's the list of the commands that failed out of memory (stop at 2.7GB memory consumed):
git for-each-ref
git rev-list --branches --tags
 - this command succeeded :
git rev-list --branches (80MB consumed)
 - some packing have been done :
git repack -a -d -f 
git pack-ref --all
(on the big machine, it fails on mine)
after the git commands keep failing out of memory, 'git rev-list --branches' included.
 - there is 2159 refs in the repository.
 - git count-objects -v gives :

count: 0 size: 0 in-pack: 133986 packs: 1 size-pack: 365678 prune-packable: 0 garbage: 0

 - I still have a copy of the cvs and git repositories for testing.

Thanks in advance for any help, Frédéric Heulin.

Message 1 of 1 in “[problem] out of memory”
  1. Frédéric HeulinJan 27, 2010

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.