git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Harald Dunkel <harald.dunkel@aixigo.de>
Cc: git@vger.kernel.org
Subject: Re: git-lfs integration?
Date: Thu, 10 Jan 2019 03:09:59 +0000	[thread overview]
Message-ID: <20190110030959.GL423984@genre.crustytoothpaste.net> (raw)
In-Reply-To: <79fd2b4e-243c-a9f5-3485-2954fb0f50ef@aixigo.de>

[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]

On Tue, Jan 08, 2019 at 04:16:41PM +0100, Harald Dunkel wrote:
> Hi folks,
> 
> I wonder why git-lfs is needed to efficiently handle large files
> in git. Would it be reasonable to integrate this functionality
> into the native git?

Most of the problems Git has with handling large files aren't really
problems if you have unlimited resources, but they are practical
problems in some situations.

Git doesn't really handle files that exceed memory capacity very well.
In order to deltify files, we need to have them in memory, so the option
is either to not deltify large files and have a lot of storage used, or
deltify and spend a lot of CPU and memory compressing, decompressing,
and deltifying them.

This means that Git can require a lot of resources to store and repack
large files. This is not only a problem on your system, but on whatever
remote system you host your repos on (your own server, GitHub, GitLab,
etc.). Your host, while probably having more resources than your local
machine, also probably has more repos as well.

Git LFS makes the trade-off to store files uncompressed and only copy
the needed files from the server to your system. That means that you
don't need to bloat your local clone with files you may never check out,
but you have the downside that your clone isn't necessarily complete.

I'm a maintainer of Git LFS, and I'm perfectly happy with solutions that
help Git handle large files better. Ævar gave a great explanation of
some of the work that's going on in this regard, and I'm also happy to
hear about other improvements that may come up as well.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

      parent reply	other threads:[~2019-01-10  3:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 15:16 git-lfs integration? Harald Dunkel
2019-01-08 15:45 ` Ævar Arnfjörð Bjarmason
2019-01-09  6:10   ` Harald Dunkel
2019-01-10  3:09 ` brian m. carlson [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190110030959.GL423984@genre.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=harald.dunkel@aixigo.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).