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

Re: Average size of git bookkeeping data (related to Using git as a general backup mechanism)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 14, 2006, 00:02 UTC
Message-ID
<Pine.LNX.4.63.0612140058000.3635@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20061213193149.43284.qmail@web86909.mail.ukl.yahoo.com>
Hi,
On Wed, 13 Dec 2006, David Tweed wrote:
> How big is the "metadata" or "bookeeping data" in git related to a 
> commit?

In my experience, a single commit (with the trees and blobs being reachable from it) takes about the same space in a pack as the corresponding tar ball.

When you add revisions, the pack grows approximately with the compressed patch size.

So, if you can estimate the size of the initial tar ball and the size of the subsequent patches, you have a ballpark figure of the metadata size of the git repository. (This is for the bare case; for the regular case you have to add the size of a checked out tree, of course.)

Hth, Dscho

Previous: David TweedNext: David Lang
Message 2 of 3 in “Average size of git bookkeeping data (related to Using git as a general backup mechanism)”
  1. David TweedDec 13, 2006
  2. Johannes SchindelinDec 14, 2006
  3. David LangDec 20, 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.