[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cl-lib warnings
From: |
Sean Whitton |
Subject: |
Re: cl-lib warnings |
Date: |
Fri, 06 Jan 2023 10:58:06 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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