git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andreas Krey <a.krey@gmx.de>
To: Shawn Pearce <spearce@spearce.org>
Cc: Chico Sokol <chico.sokol@gmail.com>,
	John Szakmeister <john@szakmeister.net>,
	git <git@vger.kernel.org>
Subject: fetch delta resolution vs. checkout (was: java zlib woes)
Date: Tue, 4 Jun 2013 12:18:36 +0200	[thread overview]
Message-ID: <20130604101836.GH22784@inner.h.apk.li> (raw)
In-Reply-To: <20130527041146.GJ9448@inner.h.apk.li>

On Mon, 27 May 2013 06:11:46 +0000, Andreas Krey wrote:
...
> 
> I now have a full test case (involving a generated repo just shy of 1GB)
> that will reproduce that hang. Will look up the existing jgit bug to
> report there.

On https://bugs.eclipse.org/bugs/show_bug.cgi?id=394078

A question: The delta decoding. If I understand correctly,
git and jgit do verify the packfile content after fetching/cloning,
and need to resolve any deltified files in the pack.

And when checking out a commit it needs this to again for the
files that are being checked out?

Because we now have the phenomenon that the packfile is fetched
ok, but a checkout then hangs (100%) CPU on one of the large files,
and on one that should, according to core.bigfilethreshold, not
even be deltified.

(Setting core.bigfilethreshold to 20m in the source repo (C git)
gets jgit to no longer hang in the fetch/delta resolution phase.
And it doesn't look like jgit would repack the pack file, and
uses it as it was received plus 20 bytes at the end.)

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800

  reply	other threads:[~2013-06-04 10:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 21:21 Reading commit objects Chico Sokol
2013-05-21 21:25 ` Felipe Contreras
2013-05-21 21:37 ` John Szakmeister
2013-05-21 22:18   ` Chico Sokol
2013-05-21 22:22     ` Junio C Hamano
2013-05-21 22:33       ` Chico Sokol
2013-05-21 23:34         ` Jonathan Nieder
2013-05-22  5:54         ` Shawn Pearce
2013-05-22  4:51     ` java zlib woes (was: Reading commit objects) Andreas Krey
2013-05-22  5:56       ` Shawn Pearce
2013-05-27  4:11         ` Andreas Krey
2013-06-04 10:18           ` Andreas Krey [this message]
2013-05-22  5:59     ` Reading commit objects Shawn Pearce
2013-05-22 14:20       ` Chico Sokol
2013-05-22 20:02         ` Shawn Pearce
2013-05-22 14:25       ` Chico Sokol
2013-05-22 14:47         ` Chico Sokol
2013-05-22 19:59         ` Shawn Pearce
2013-05-21 22:20 ` Junio C Hamano

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=20130604101836.GH22784@inner.h.apk.li \
    --to=a.krey@gmx.de \
    --cc=chico.sokol@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=john@szakmeister.net \
    --cc=spearce@spearce.org \
    /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).