From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Convert README.org to plain text README while installing package Date: Wed, 08 Jun 2022 13:37:28 -0400 Message-ID: References: <87leuca7v7.fsf@disroot.org> <87czfopmsd.fsf@gnu.org> <87h74ztshe.fsf@gmx.de> <871qw31ois.fsf@yahoo.com> <878rqb5egg.fsf@localhost> <87czfjs4h4.fsf@localhost> <837d5r5jfb.fsf@gnu.org> <87leu7qkym.fsf@localhost> <87r13zyxax.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15704"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Eli Zaretskii , luangruo@yahoo.com, michael.albinus@gmx.de, acm@muc.de, stefan@marxist.se, tsdh@gnu.org, akib@disroot.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 08 19:38:48 2022 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 1nyzdo-0003sN-8K for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Jun 2022 19:38:48 +0200 Original-Received: from localhost ([::1]:33500 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nyzdm-0004Wa-Rc for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Jun 2022 13:38:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47712) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nyzcf-0003kA-B0 for emacs-devel@gnu.org; Wed, 08 Jun 2022 13:37:37 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:53218) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nyzcc-0007XX-Fc; Wed, 08 Jun 2022 13:37:35 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 6C3C71006F8; Wed, 8 Jun 2022 13:37:31 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id E4D1D100135; Wed, 8 Jun 2022 13:37:29 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1654709849; bh=ijo2o5f3ihJr9OFK7PBhiPnk4f7ND4Kao08U6F/bY1I=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=h4dKdGvifA8fkFz51snmfdismPgyPQM5q4flLhb9lbiQ5/xxyjj0wn0bRJGP8SRDP kV5uQuR7pw3axct/o4Z3boQkzuFMlkigtHdOH2BBrPxX8WbcMNDlxdYxyCXI/35prQ I3wVtsYlIIUa3CtOm/LNloZL11hfByEs7bnatRW1vB86gLnKsskWK7SZdPfdVifJIS wSVKfVNcz7tGmBh/llxM0oVPaLz+/QNoatxupZ/Z2RpnVUJpGVTgPK5sThiUi+0xyr pFx2wNpkNqGN0cmClJFZYWTuvHjAawcrDfWuflPKU7X/PbJWsbOe2HioD4tdR0ktDX tbMCDIRpnT/OA== Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D49C0120314; Wed, 8 Jun 2022 13:37:29 -0400 (EDT) In-Reply-To: <87r13zyxax.fsf@localhost> (Ihor Radchenko's message of "Wed, 08 Jun 2022 23:44:38 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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" Xref: news.gmane.io gmane.emacs.devel:290951 Archived-At: > Moreover, I know myself that the actual memory allocation is done down > in org-perist-read when running (read (current-buffer)). I got memory > profiler wrong significant amount of time to learn not to trust it too > much. Indeed, the memory profiler is not very reliable. Some of that is a conscious implementation choice (e.g. we take samples when a whole new 16KB block is allocated to be divided into several smaller objects rather than for every object allocation). Other problems are things for which I don't have an explanation (and haven't spent the time to try and track them down). I've still found it useful to help figure out in which part of the code most of the allocation takes place, but you need to supplement it without your own knowledge of what the code does :-( Stefan