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

RAM consumption when working with the gcc repo

From
Jon Smirl <jonsmirl@gmail.com>
Date
Dec 7, 2007, 20:07 UTC
Message-ID
<9e4733910712071207p750c14f4h7abc5d637da3a478@mail.gmail.com>

I noticed two things when doing a repack of the gcc repo. First is that the git process is getting to be way too big. Turning off the delta caches had minimal impact. Why does the process still grow to 4.8GB?

Putting this in perspective, this is a 4.8GB process constructing a 330MB file. Something isn't right. Memory leak or inefficient data structure?

The second issue is that the repack process slows way down on the last 10% of the packing process. I don't believe this was caused by swapping since my disk light wasn't on. It takes a long to do the last 10% as it did for the first 70%. This seems to be correlated with the size of the process getting so large.

-- 
Jon Smirl
jonsmirl@gmail.com
Next: david@lang.hm
Message 1 of 15 in “RAM consumption when working with the gcc repo”
  1. Jon SmirlDec 7, 2007
  2. david@lang.hmDec 7, 2007
  3. Marco CostalbaDec 7, 2007
  4. Nicolas PitreDec 7, 2007
  5. Jon SmirlDec 7, 2007
  6. Marco CostalbaDec 7, 2007
  7. Johannes SchindelinDec 8, 2007
  8. Marco CostalbaDec 8, 2007
  9. Jon SmirlDec 7, 2007
  10. Jon SmirlDec 7, 2007
  11. Jon SmirlDec 7, 2007
  12. Martin KoeglerDec 8, 2007
  13. Jeff KingDec 7, 2007
  14. Jeff KingDec 7, 2007
  15. Jon SmirlDec 7, 2007

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.