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: Sat, 11 Mar 2023 13:53:03 +0000 Message-ID: <871qlvwg1s.fsf@localhost> References: <20230310110747.4hytasakomvdyf7i.ref@Ergus> <20230310110747.4hytasakomvdyf7i@Ergus> <87a60k657y.fsf@web.de> <838rg4zmg9.fsf@gnu.org> <87ttys4dge.fsf@web.de> <83sfebyepp.fsf@gnu.org> <87ttyru4zt.fsf@web.de> <83fsabyb41.fsf@gnu.org> <87mt4jtpqf.fsf@web.de> <83ilf7wi48.fsf@gnu.org> <878rg3wh2f.fsf@localhost> <83cz5fwggd.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="11492"; 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 Sat Mar 11 14:52: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 1pazdr-0002jM-0Y for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Mar 2023 14:52:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pazdQ-0002GH-MN; Sat, 11 Mar 2023 08:51:44 -0500 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 1pazdO-0002Fy-Rj for emacs-devel@gnu.org; Sat, 11 Mar 2023 08:51:42 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pazdN-0002FV-97 for emacs-devel@gnu.org; Sat, 11 Mar 2023 08:51:42 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 04DCD240385 for ; Sat, 11 Mar 2023 14:51:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1678542699; bh=X1q4pgImMXyrdaPbWxnlH4HAoD3Ix4TbFFOjI9RR3Gw=; h=From:To:Cc:Subject:Date:From; b=FbKpwWzQETp6tDahtCW1SW38mMPhvAG6KVrzOhzntWWXXoXEocwuGUfyFrycw5Qaa +SQwE3LGOqublpP+E4NjbNuaHB9rUIv37o2dpBOpBuBIrLwIMZTbiLC8e/iHPzm4Ys 3AGkwaHx3M/Poded+HZCAtmXOi+f9RfDmbVKmOVwylyZT1im32O2t9PG6alZsrVp9o MMWd+m1yPjgEgJu3rwSbtGuFx+uWYsauvM1Qt8aKM418Tz9xgk5qKctsUIwn4ktA4T PBpMIo18wC0tRo983c+Hqur/4Peb/Pc50I5rAMqevgO9/L/KnQKBQXwVCm0XAk/zOF FECCF5cDzgbBA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PYkqD0XXTz9rxB; Sat, 11 Mar 2023 14:51:36 +0100 (CET) In-Reply-To: <83cz5fwggd.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.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:304315 Archived-At: Eli Zaretskii writes: >> (pcase (* (car (memory-info)) ; in kb >> 1000) >> (`nil 800000) ; 800kb, old default >> (ram >> (let ((scaled-threshold >> (* 0.7e-2 ; 800kb/128Mb for low-end systems. >> ram))) >> (min >> (* 100 1000 1000) ; upper limit to avoid fragmentation >> scaled-threshold)))) > > The above implicitly assumes that gc-cons-threshold is the absolute > ceiling of the memory Emacs can allocate. But that is not what that > threshold means and how it is used. Even with the default threshold > of 800K a running Emacs session can allocate much more than 800K > bytes. No. I took into account the fact that `gc-cons-threshold' is paired with `gc-cons-percentage'. The latter scales with Emacs memory usage. For the former, it makes sense to scale with available memory until `gc-cons-percentage' takes over. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at