From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pierre Habouzit <madcoder@debian.org>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
spearce@spearce.org, "Git ML" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] index-pack: never prune base_cache.
Date: Wed, 23 Jul 2008 14:46:38 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807231436440.8986@racer> (raw)
In-Reply-To: <20080723132031.GC20614@artemis.madism.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1220 bytes --]
Hi,
On Wed, 23 Jul 2008, Pierre Habouzit wrote:
> On Wed, Jul 23, 2008 at 01:09:40PM +0000, Johannes Schindelin wrote:
> > On Wed, 23 Jul 2008, Björn Steinbrink wrote:
> > > The patch itself should be fine.
> >
> > No, since it opens the whole issue of memory explosion again, the same
> > issue Shawn's original patch tried to fix.
>
> No it won't. Indeed the issue is with fix_unresolved_deltas that
> sometimes put at the root of the chain (in base_cache) something that
> comes from our store, not the pack we are writing. Then starts a delta
> chain resolution.
If it comes from our store, we should have _no_ problem reconstructing the
object.
> It won't explode in memory at all, we just keep the first data of a
> delta chain in memory, that's all. It indeed consumes more memory, but
> we talk about *one* single object per delta chain because we're too lazy
> to memorize where it comes from. It's probably not much of an explosion.
"Probably".
> We also waste that object even when it's from our own pack. Well, I'd
> say "too bad".
And I say it's dirty, and since the pack code traditionally is one of the
cleanest parts of Git, coming from Nico, let's not change that, okay?
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-23 13:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 23:17 regression in 92392b4 Pierre Habouzit
2008-07-22 23:34 ` Johannes Schindelin
2008-07-23 0:41 ` Shawn O. Pearce
2008-07-23 0:58 ` Johannes Schindelin
2008-07-23 1:09 ` Pierre Habouzit
2008-07-23 1:20 ` Johannes Schindelin
2008-07-22 23:37 ` Pierre Habouzit
2008-07-23 10:14 ` Björn Steinbrink
2008-07-23 10:22 ` Pierre Habouzit
2008-07-23 10:38 ` Pierre Habouzit
2008-07-23 10:49 ` Johannes Schindelin
2008-07-23 10:56 ` Björn Steinbrink
2008-07-23 11:19 ` Pierre Habouzit
2008-07-23 11:37 ` Johannes Schindelin
2008-07-23 11:50 ` Pierre Habouzit
2008-07-23 12:00 ` Björn Steinbrink
2008-07-23 12:11 ` [PATCH] index-pack: never prune base_cache Pierre Habouzit
2008-07-23 12:52 ` Björn Steinbrink
2008-07-23 13:09 ` Johannes Schindelin
2008-07-23 13:20 ` Pierre Habouzit
2008-07-23 13:46 ` Johannes Schindelin [this message]
2008-07-23 13:44 ` Björn Steinbrink
2008-07-23 14:41 ` Johannes Schindelin
2008-07-23 15:30 ` Pierre Habouzit
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=alpine.DEB.1.00.0807231436440.8986@racer \
--to=johannes.schindelin@gmx.de \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox