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

Git server memory requirements

From
CBCliff Brake <cbrake@bec-systems.com>
Date
Mar 21, 2014, 17:38 UTC
Message-ID
<CAOd_LFwDQZGHo+gUhNKzvT2B8iavN_75KjwwC6P=W3z11d9zAw@mail.gmail.com>

I'm trying to get an idea how much memory is required for a git server that is hosting linux kernel repos.

What we're seeing is that git uses around 1GB of RAM on the server when a user does a clone of the Linux kernel source over ssh. Does this seem about right? Is this amount fixed, or arbitrary (trade-off memory for speed). It seems subsequent concurrent clones use less memory.

Is there any practical way to reduce the memory usage? We're running into occasional issues if there are multiple clones at once.

Is setting gc.auto=0 a good idea for large kernel repos? The idea is we can repack manually or in a cron on weekends rather than during user operations. However, manually running a git gc seems to use about as much memory as a user clone.

It may be that our EC2 small instance (2.5GB) is not up to the task, but would like to understand options (we can easily trade off some speed for less memory if we can) before upgrading.

Thanks, Cliff

Next: Robin H. Johnson
Message 1 of 2 in “Git server memory requirements”
  1. Cliff BrakeMar 21, 2014
  2. Robin H. JohnsonMar 21, 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.