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: cl-lib warnings Date: Fri, 06 Jan 2023 20:14:13 +0200 Message-ID: <83y1qfttsa.fsf@gnu.org> References: <86o7s3lsnx.fsf@mail.linkov.net> <86bknx8783.fsf@mail.linkov.net> <837cylapt4.fsf@gnu.org> <83wn6kamwr.fsf@gnu.org> <83len0aldq.fsf@gnu.org> <87v8lkmd9z.fsf@melete.silentflame.com> <83358ow1yy.fsf@gnu.org> <87358nmtox.fsf@melete.silentflame.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30028"; mail-complaints-to="usenet@ciao.gmane.io" Cc: lekktu@gmail.com, joaotavora@gmail.com, juri@linkov.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Sean Whitton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 06 19:14:42 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 1pDrEo-0007dC-EG for ged-emacs-devel@m.gmane-mx.org; Fri, 06 Jan 2023 19:14:42 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pDrEF-0005QA-1g; Fri, 06 Jan 2023 13:14:07 -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 1pDrEB-0005Q2-Mz for emacs-devel@gnu.org; Fri, 06 Jan 2023 13:14:03 -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 1pDrE5-0003c9-2u; Fri, 06 Jan 2023 13:14:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=khddMK6Xmon9dWvHP1JYlPdfMrAozino0dAZfr9vv9I=; b=HL5hTmELI57U LSLYMmbdT6tAubXzmbzpGbj+NpF6/6B6coU9iwKvfqqkyKxXjx5tbDQPAYWWaYr/Iil40BqflsfKf e2BgHv5Wza23219wgcU0PQfchGVyxHOsibzyry8SNCEwFJnMo8ZkrO+I93xlG4U8ZFZuzGHgO+JY/ YMoyowa7VqRd1yfgRoAqcrp12sH/D3wS+/+rLZDtOXB/0L0INSFoUqu5GcI8DOZ2u1elTn66F0p6z pDpoh7kl2vreiF09LNrbo/0TvbKPPtmR/mrPaIdL9lZD7ETsRhvpgGPhZvXGhx5/I+klPnrcuU8qS 4CAqtdsvgA5rouuDR/XSzw==; 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 1pDrE3-0007c2-3m; Fri, 06 Jan 2023 13:13:56 -0500 In-Reply-To: <87358nmtox.fsf@melete.silentflame.com> (message from Sean Whitton on Fri, 06 Jan 2023 10:58:06 -0700) 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:302261 Archived-At: > From: Sean Whitton > Cc: lekktu@gmail.com, joaotavora@gmail.com, juri@linkov.net, > monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Fri, 06 Jan 2023 10:58:06 -0700 > > > In general, I'm worried by IMO too nonchalant attitude towards > > preloading more and more into Emacs. We should actively try to keep > > the memory footprint of the Emacs process in check. It is true that > > each package we add increases the footprint by a small amount, but > > those small amounts eventually add up to a sum that is significant. > > On my system starting "emacs -q" with various versions of Emacs > > produces the following memory footprint values: > > > > emacs 22.1 10.6 MiB > > emacs 23.1 11.5 MiB > > emacs 24.1 13.4 MiB > > emacs 25.1 32.5 MiB > > emacs 26.1 35.5 MiB > > emacs 27.1 25.1 MiB > > emacs 28.2 26.7 MiB > > > > Granted, not all of the increase is due to preloading more Lisp, but > > some of it is, and so IMO we should resist the temptation to add more > > just because it saves us some 'require's. > > What sort of target do you think we should have? I don't think I understand the question. What do you mean by "target" here?