From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, joaotavora@gmail.com, juri@linkov.net,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: cl-lib warnings
Date: Fri, 06 Jan 2023 10:58:06 -0700 [thread overview]
Message-ID: <87358nmtox.fsf@melete.silentflame.com> (raw)
In-Reply-To: <83358ow1yy.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Jan 2023 09:34:29 +0200")
Hello,
On Fri 06 Jan 2023 at 09:34AM +02, Eli Zaretskii wrote:
> The "almost always" is not a numerical criterion, its "almost" part is
> intended to cover the cases where the package is _always_ loaded at
> startup, but only in some configurations of Emacs. Like something
> that happens only in GTK builds. So counting the number of Lisp
> packages that require cl-lib is not going to change my mind.
Okay, thanks.
> 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?
--
Sean Whitton
next prev parent reply other threads:[~2023-01-06 17:58 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvv8mc4eax.fsf@iro.umontreal.ca>
[not found] ` <86o7s3lsnx.fsf@mail.linkov.net>
2022-12-20 18:42 ` cl-lib warnings (was: bug#60102: Move gv-expander of substring to cl-lib) Stefan Monnier
2022-12-21 8:37 ` cl-lib warnings Juri Linkov
2022-12-21 12:45 ` Eli Zaretskii
2022-12-21 12:57 ` João Távora
2022-12-21 13:47 ` Eli Zaretskii
2022-12-21 14:04 ` João Távora
2022-12-21 14:20 ` Eli Zaretskii
2022-12-21 14:35 ` João Távora
2022-12-21 14:50 ` Juanma Barranquero
2022-12-21 14:55 ` João Távora
2022-12-21 14:57 ` Juanma Barranquero
2022-12-21 15:08 ` João Távora
2022-12-26 3:13 ` Milan Glacier
2022-12-26 15:10 ` João Távora
2022-12-26 23:48 ` Milan Glacier
2022-12-27 0:05 ` João Távora
2022-12-27 3:43 ` Tim Cross
2022-12-27 10:16 ` Lynn Winebarger
2022-12-27 13:00 ` Stefan Kangas
2022-12-21 17:14 ` Eli Zaretskii
2022-12-21 22:33 ` Juanma Barranquero
2022-12-22 7:13 ` Eli Zaretskii
2022-12-22 7:23 ` Juanma Barranquero
2022-12-22 8:53 ` Eli Zaretskii
2022-12-22 22:24 ` Yuan Fu
2022-12-22 23:56 ` Stefan Monnier
2022-12-23 7:30 ` Eli Zaretskii
2022-12-23 23:42 ` Yuan Fu
2022-12-24 0:24 ` Juanma Barranquero
2022-12-24 14:08 ` Stefan Monnier
2022-12-24 14:39 ` Juanma Barranquero
2022-12-24 19:13 ` Tomas Hlavaty
2022-12-24 0:26 ` João Távora
2022-12-24 10:33 ` Philip Kaludercic
2022-12-24 11:01 ` João Távora
2022-12-26 0:11 ` cl-loop and plists vs alists Philip Kaludercic
2022-12-26 0:35 ` João Távora
2022-12-26 21:06 ` Bob Rogers
2022-12-24 22:59 ` cl-lib warnings Sean Whitton
2022-12-25 1:21 ` Stefan Monnier
2022-12-25 2:39 ` package-initialize was " T.V Raman
2022-12-25 4:11 ` T.V Raman
2022-12-26 0:01 ` Stefan Monnier
2022-12-26 2:18 ` T.V Raman
2022-12-25 7:02 ` tomas
2022-12-25 9:55 ` João Távora
2022-12-25 11:33 ` tomas
2022-12-26 4:47 ` Sean Whitton
2022-12-24 6:40 ` Eli Zaretskii
2022-12-24 13:01 ` Dmitry Gutov
2023-01-06 5:40 ` Sean Whitton
2023-01-06 7:34 ` Eli Zaretskii
2023-01-06 17:58 ` Sean Whitton [this message]
2023-01-06 18:14 ` Eli Zaretskii
2023-01-06 19:03 ` Sean Whitton
2023-01-06 19:45 ` Eli Zaretskii
2022-12-21 14:15 ` Eli Zaretskii
2022-12-21 17:53 ` Stefan Monnier
2022-12-24 22:55 ` Sean Whitton
2022-12-25 7:05 ` tomas
2022-12-25 8:29 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87358nmtox.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).