From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Indentation and gc Date: Sat, 11 Mar 2023 15:46:30 +0200 Message-ID: <83bkkzwgcp.fsf@gnu.org> References: <20230310110747.4hytasakomvdyf7i.ref@Ergus> <20230310110747.4hytasakomvdyf7i@Ergus> <87a60k657y.fsf@web.de> <838rg4zmg9.fsf@gnu.org> <87ttyrwobj.fsf@localhost> <20230311111730.fatow74xnbel7t3f@Ergus> <83o7ozwju8.fsf@gnu.org> <87jzznwjh3.fsf@localhost> <83jzznwjeh.fsf@gnu.org> <87fsabwirg.fsf@localhost> <83h6urwhu0.fsf@gnu.org> <875yb7wgpd.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27329"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spacibba@aol.com, arne_bab@web.de, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 11 14:47:17 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 1pazZ5-0006to-PE for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Mar 2023 14:47:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pazYg-00010R-OY; Sat, 11 Mar 2023 08:46:50 -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 1pazYb-0000yg-JV for emacs-devel@gnu.org; Sat, 11 Mar 2023 08:46:46 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pazYb-0001f7-16; Sat, 11 Mar 2023 08:46:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=wMGzprRSdc9lj88JPeIQPrbM8srg251rDLhQJdc0Uwg=; b=WRBArjhHinVwaHnuxzwF TJyG8bZFRlAGlgQtLPwtDIi8FB1H0Xw8I2vOVWecF0t9uTzSuW9nSVnxuhXq35dOHMGPRAMQL39qt BJAFfns4glmide93ocdk+pFpwh7CtA419bQMATHco7ZIxrmX6ilmxuDy1dSoTwT+Xi4Ug1YR8eoKX G8U6jpunAV5+ooiESbF5gaxF1Jp+Wg8xQosctJdDLHn+r3nyQicXCOe+vidNvYQ1cCdpBO5ZwOdcM kjY4nzyPTh2iXfQezsF3B8IeYui58uOBIG+3mmiw6KrG7JfL3/6PbO09FgbZvkrCK38aoedPMbJcQ TlqtMDfHbn6H3w==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pazYa-0004Cc-9v; Sat, 11 Mar 2023 08:46:44 -0500 In-Reply-To: <875yb7wgpd.fsf@localhost> (message from Ihor Radchenko on Sat, 11 Mar 2023 13:38:54 +0000) 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:304314 Archived-At: > From: Ihor Radchenko > Cc: spacibba@aol.com, arne_bab@web.de, emacs-devel@gnu.org > Date: Sat, 11 Mar 2023 13:38:54 +0000 > > What about expanding the relevant paragraph in the manual with examples > when increasing the threshold too much is dangerous? > > The initial threshold value is ‘GC_DEFAULT_THRESHOLD’, defined in > ‘alloc.c’. Since it’s defined in ‘word_size’ units, the value is > 400,000 for the default 32-bit configuration and 800,000 for the > 64-bit one. If you specify a larger value, garbage collection will > happen less often. This reduces the amount of time spent garbage > collecting, but increases total memory use. You may want to do > this when running a program that creates lots of Lisp data. > However, we recommend against increasing the threshold for > prolonged periods of time, and advise that you never set it higher > than needed for the program to run in reasonable time. Using > thresholds higher than necessary could potentially cause > system-wide memory pressure, and should therefore be avoided. What is there to expand? It already says all that people need to understand before they play dangerous games with the threshold.