From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: Move to git is imminent - awaiting Stefan's approval Date: Sun, 12 Jan 2014 11:29:42 +0100 Organization: Linux Private Site Message-ID: <87k3e5xzl5.fsf@Rainer.invalid> References: <8761pvvoq1.fsf@rosalinde.fritz.box> <83d2k3sqqz.fsf@gnu.org> <52CC2D45.1000908@alice.it> <83a9f7sosr.fsf@gnu.org> <52CC5ED3.2000903@alice.it> <83d2k2fkg1.fsf@gnu.org> <87txdenwz3.fsf@igel.home> <20140112062722.GA15615@hysteria.proulx.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1389522611 10875 80.91.229.3 (12 Jan 2014 10:30:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Jan 2014 10:30:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 12 11:30:18 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W2IJ5-0005le-OQ for ged-emacs-devel@m.gmane.org; Sun, 12 Jan 2014 11:30:15 +0100 Original-Received: from localhost ([::1]:37109 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W2IJ5-000739-8N for ged-emacs-devel@m.gmane.org; Sun, 12 Jan 2014 05:30:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53776) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W2IIw-0006zx-9x for emacs-devel@gnu.org; Sun, 12 Jan 2014 05:30:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W2IIn-0001F0-PD for emacs-devel@gnu.org; Sun, 12 Jan 2014 05:30:06 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:53088) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W2IIn-0001Ek-IT for emacs-devel@gnu.org; Sun, 12 Jan 2014 05:29:57 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W2IIj-0005PD-LK for emacs-devel@gnu.org; Sun, 12 Jan 2014 11:29:53 +0100 Original-Received: from pd9eb3947.dip0.t-ipconnect.de ([217.235.57.71]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Jan 2014 11:29:53 +0100 Original-Received: from Stromeko by pd9eb3947.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Jan 2014 11:29:53 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pd9eb3947.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:EaFnB13lvTX+utfEWgkC1Rs9BVw= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:168166 Archived-At: Bob Proulx writes: > I have a couple of questions if someone already has the clone > available for a test. Does a clone from the agressively repacked to > 327M repository remain similarly compacted when cloned again from it? Once the whole repository is repacked it keeps those pack decisions, also across clones. The pack strategy for new commits would typically be near-optimal unless someone fast-imported a large branch again (in that case it should preferrably be locally repacked before getting pushed to Savannah). > If an agressively repacked repository is again repacked but this time > without the --agressive option does the size stay around 327M or does > it get expanded on the subsequent pass? I don't think a plain gc will expand any old packs, in any case the benefits of "git gc --agressive" are supposed to last for a long time. >(Wondering if we can periodically run 'git gc --agressive' on the >larger git repositories at a niced background task priority but not too >often and still achieve a good benefit for the time between agressive >repacks.) Just a manual "git gc --aggressive" once in a while should be enough. If you are going to do it as a cron-job, I'm not sure if it's a good idea to nice it. I think you'd rather want to limit the number of threads it uses, which also limits the memory footprint, which is probably the bigger problem anyway and should probably be tuned further depending on how beefy the server is. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada