From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [PATCH] Set hard limit on delta chain depth Date: Tue, 6 Dec 2011 13:56:36 -0500 Message-ID: <20111206185636.GC9492@sigill.intra.peff.net> References: <1323068688-31481-1-git-send-email-pclouds@gmail.com> <4EDE2C95.5040804@alum.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Nguyen Thai Ngoc Duy , Michael Haggerty , kusmabite@gmail.com, git@vger.kernel.org, Junio C Hamano To: Shawn Pearce X-From: git-owner@vger.kernel.org Tue Dec 06 19:56:43 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RY0C3-0005TM-BE for gcvg-git-2@lo.gmane.org; Tue, 06 Dec 2011 19:56:43 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751836Ab1LFS4j (ORCPT ); Tue, 6 Dec 2011 13:56:39 -0500 Received: from 99-108-226-0.lightspeed.iplsin.sbcglobal.net ([99.108.226.0]:41445 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751320Ab1LFS4i (ORCPT ); Tue, 6 Dec 2011 13:56:38 -0500 Received: (qmail 7113 invoked by uid 107); 6 Dec 2011 19:03:16 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.84) with ESMTPA; Tue, 06 Dec 2011 14:03:16 -0500 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Tue, 06 Dec 2011 13:56:36 -0500 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, Dec 06, 2011 at 10:12:54AM -0800, Shawn O. Pearce wrote: > > Normal creators (i.e. C Git) use default depth 50 so we should be safe. > > JGit is also a "normal creator", and it sometimes produces chains > deeper than 50. Junio identified a 255 deep chain a week or two ago. > Some people have repacked their repositories very aggressively with > deeper chains when they are trying to optimize for space and don't > access historical revisions very often. I doubt anyone has packed > deeper than 120ish intentionally... but we shouldn't assume that in > the code. "git gc --aggressive" will set the depth to 250. -Peff