From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Indentation and gc Date: Thu, 16 Mar 2023 10:27:47 +0000 Message-ID: <87sfe5t2ho.fsf@localhost> References: <20230310110747.4hytasakomvdyf7i.ref@Ergus> <87mt4jtpqf.fsf@web.de> <83ilf7wi48.fsf@gnu.org> <878rg3wh2f.fsf@localhost> <83cz5fwggd.fsf@gnu.org> <871qlvwg1s.fsf@localhost> <83a60jwf9l.fsf@gnu.org> <871qluuk3y.fsf@localhost> <831qluuj7e.fsf@gnu.org> <87v8j6t3i9.fsf@localhost> <83v8j6t2ib.fsf@gnu.org> <87zg8gbsch.fsf@localhost> <838rg0u0fd.fsf@gnu.org> <87wn3ky7rz.fsf@localhost> <831qlstwoi.fsf@gnu.org> <87r0tsy1c4.fsf@localhost> <83wn3jseyt.fsf@gnu.org> <87mt4eqpfd.fsf@localhost> <83zg8eqinu.fsf@gnu.org> <87h6umqig6.fsf@localhost> <83y1nyqenq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9183"; mail-complaints-to="usenet@ciao.gmane.io" Cc: arne_bab@web.de, spacibba@aol.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 16 11:27:12 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pckpD-00029N-Rp for ged-emacs-devel@m.gmane-mx.org; Thu, 16 Mar 2023 11:27:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pckoN-0002R0-PA; Thu, 16 Mar 2023 06:26:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pckoL-0002QX-5G for emacs-devel@gnu.org; Thu, 16 Mar 2023 06:26:17 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pckoJ-00084Y-75 for emacs-devel@gnu.org; Thu, 16 Mar 2023 06:26:16 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id D50172403F4 for ; Thu, 16 Mar 2023 11:26:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1678962372; bh=o7ny/e9x1i3LGlntNmuSQdrk9ZWrFVs20d9ZMPlaVzE=; h=From:To:Cc:Subject:Date:From; b=ro6UKIHkXmFppcg33m9CBDBnN5CfsMx9G7aegGVXCcGPEF+a1IR5RmYYjq9iBN6XP FsR4vSyv7f9QPih7kKNVptnLHnmPJ0v3kNXcqfPFYh9Ot861H+80Kj4V/XyiVlApK+ m9NjCclneQHNVwltW+oEvH3+VEt6J5Kem8CxyXM629y/ycB6wamdy1b+eecysNpzjc rSjdXtFPmOadnVvoyQA24ag+WgIACs6qTvt8Uuo5JySX2FaCmfML1dZz9DetpF7//F aDStS2IP+LnAHeMxwJd6r2KivXVSK5YnKvg11cAUQMe8Hvjjckxyu3DuRXk2sIOiU0 kZqCbGN3X7I4A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Pck1t72rZz9rxK; Thu, 16 Mar 2023 11:26:07 +0100 (CET) In-Reply-To: <83y1nyqenq.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304516 Archived-At: Eli Zaretskii writes: >> What exactly should we use as a metric for the effects of >> gc-cons-threshold changes? > > I guess the output of memory-info should be good, in addition to > memory-limit. I am not sure what it will convey to us. System memory state greatly depends on other programs running alongside Emacs. I do not see much use to track (memory-info) for every GC. Just initially, to catch system memory stats. > But that's the possible downside of higher GC thresholds; other > important indications are the time spent in GC and the average > duration of a GC cycle. Sure. gcs-done and gc-elapsed can be recorded after every GC. gc-elapsed will directly provide data on total GC duration and running difference of gc-elapsed will provide detailed statistics on GC cycle duration. I will now try to record the data on my sessions and share it later. We can then see what useful information can actually be extracted. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at