From: Lars Schneider <larsxschneider@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: [git-sizer] Implications of a large commit object
Date: Wed, 14 Mar 2018 09:14:46 +0100 [thread overview]
Message-ID: <953C263C-6ECA-46AC-849C-8D1A38378654@gmail.com> (raw)
Hi,
I am using Michael's fantastic Git repo analyzer tool "git-sizer" [*]
and it detected a very large commit of 7.33 MiB in my repo (see chart
below).
This large commit is expected. I've imported that repo from another
version control system but excluded all binary files (e.g. images) and
some 3rd party components as their history is not important [**]. I've
reintroduced these files in the head commit again. This is where the
large commit came from.
This repo is not used in production yet but I wonder if this kind of
approach can cause trouble down the line? Are there any relevant
implication of a single large commit like this in history?
Thanks,
Lars
[*] https://github.com/github/git-sizer
[**] I know some of this stuff shouldn't be in the repo in the first
place, but I am constrained in the things I can change.
#######################################################################
## git-sizer output
Processing blobs: 543782
Processing trees: 517104
Processing commits: 43365
Matching commits to trees: 43365
Processing annotated tags: 3
Processing references: 123
| Name | Value | Level of concern |
| ---------------------------- | --------- | ------------------------------ |
| Overall repository size | | |
| * Blobs | | |
| * Total size | 18.8 GiB | ** |
| | | |
| Biggest objects | | |
| * Commits | | |
| * Maximum size [1] | 7.33 MiB | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
| * Trees | | |
| * Maximum entries [2] | 6.84 k | ** |
| | | |
| History structure | | |
| * Maximum tag depth [3] | 1 | * |
| | | |
| Biggest checkouts | | |
| * Number of directories [4] | 21.9 k | ********** |
| * Maximum path depth [4] | 18 | * |
| * Maximum path length [5] | 225 B | ** |
| * Number of files [4] | 256 k | ***** |
| * Total size of files [6] | 2.08 GiB | ** |
next reply other threads:[~2018-03-14 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 8:14 Lars Schneider [this message]
2018-03-14 8:33 ` [git-sizer] Implications of a large commit object Michael Haggerty
2018-03-14 9:40 ` Lars Schneider
2018-03-14 14:56 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=953C263C-6ECA-46AC-849C-8D1A38378654@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).