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: Tue, 14 Mar 2023 12:47:29 +0000 Message-ID: <87zg8fmrdq.fsf@localhost> References: <20230310110747.4hytasakomvdyf7i.ref@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> <87a60jtg0z.fsf@web.de> <877cvmumjq.fsf@localhost> <83356aukkh.fsf@gnu.org> <87y1o2t45i.fsf@localhost> <83wn3mt33c.fsf@gnu.org> <873568d7ac.fsf@localhost> <83a60gu0ma.fsf@gnu.org> <87zg8gy81r.fsf@localhost> <837cvku0cg.fsf@gnu.org> <87ttyoy6vy.fsf@localhost> <833568twym.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="36837"; 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 Tue Mar 14 13:46:59 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 1pc43M-0009EZ-CP for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Mar 2023 13:46:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pc42i-0000NC-Cr; Tue, 14 Mar 2023 08:46:16 -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 1pc42f-0000LY-8p for emacs-devel@gnu.org; Tue, 14 Mar 2023 08:46:13 -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 1pc42b-0008SB-T6 for emacs-devel@gnu.org; Tue, 14 Mar 2023 08:46:13 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 85E6C240571 for ; Tue, 14 Mar 2023 13:46:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1678797967; bh=719YV3iyQyapx8jXtI3H5Dg1IDIP7uJvNTI1yTjNixg=; h=From:To:Cc:Subject:Date:From; b=bJR/kL3MSfs7pvMVyN1frqv8AJJtrytiDI1Lb0i/D9L3M/+DteeJo1yegMhIgGAb5 ff60Paywh8baEYpxTN/LMMNAmgR/jDZT1K/NbboDxULvgtGPpudsnnaNr9rg+jc1Jm xH2XEPQdsdbRfH04zad5cyiNxXqVsk+H9+01DhXmZFIppJJvnRqJaNc2ngiA+HWCrp qG/LpR8BjxIH2yNEtUBEVTvl33r/9nagCCVh1qaHk2QAYxFA2qi9bmEl6b7NOMo80X AL/aErLlMLcL9pdioH9cKpqNPypCUGODVO/Kbe+sHJL56pcEe+qx8Yua62h+p9TOdG +hfTXrLtfVJYg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PbYDF32NKz6tmc; Tue, 14 Mar 2023 13:46:04 +0100 (CET) In-Reply-To: <833568twym.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:304435 Archived-At: Eli Zaretskii writes: >> Noted. Can we measure fragmentation from Elisp? > > I think only on glibc platforms, where we have malloc-info. The > output will need to be post-processed by some code, based on expert > knowledge of what the numbers mean. But can we get the output from Elisp? `malloc-info' docstring says that the output is done directly to srderr, which we cannot (?) access from Elisp. >> Does memory-limit include the fragmented memory segments? > > I think it does, although it's system-dependent. It's basically what > 'top' shows as VSIZE. At least, it can indirectly demonstrate the impact of GC threshold onto Emacs memory footprint. I guess it is what we worry about at the end. Or does the fragmentation cause other severe effects in addition to higher memory usage? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at