unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: emacs-devel@gnu.org
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 2 Oct 2015 17:19:45 -0700	[thread overview]
Message-ID: <560F1F21.7080503@dancol.org> (raw)
In-Reply-To: <m2h9m9i79j.fsf@newartisans.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On 10/02/2015 09:07 AM, John Wiegley wrote:
>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> 
>> Please always accompany such suggestions with rationale. Adding to the core
>> just because "why not?" is IMO not a good methodology. Some people still
>> care about the memory footprint of programs, so we don't want to bloat that
>> unless there are good reasons. Such reasons can only be discussed on a case
>> by case basis.
> 
> Although personally I wouldn't mind seeing cl-lib in core, for the benefit of
> Emacs I have to agree with Eli. It's not something we should do just because
> it sounds like a good idea, but because not doing it would cost us something.
> Shaving a few milliseconds from startup is not enough of a gain to be worth
> bloating core.

What's the cost of increasing the size of the dumped image? We don't
take COW faults on most of the pages, so we can discard them at will.
Because the OS can discard clean pages without writing them to the
pagefile and reconstitute them at will, transferring code from Emacs
private allocations to the dumped Emacs image _decreases_ memory
footprint. That we also shave a few milliseconds off startup is another
benefit.

If not cl-lib, then what? What is the actual bar?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-03  0:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  4:52 Should we just start dumping cl-lib? Daniel Colascione
2015-10-02  5:12 ` John Wiegley
2015-10-02  5:28   ` Daniel Colascione
2015-10-02  7:19     ` Eli Zaretskii
2015-10-02  8:07       ` Eli Zaretskii
2015-10-02  8:23       ` Artur Malabarba
2015-10-02 12:21         ` Andreas Schwab
2015-10-02 12:38           ` Artur Malabarba
2015-10-02 14:27             ` Rasmus
2015-10-02  7:21     ` Oleh Krehel
2015-10-02 11:46 ` Mark Oteiza
2015-10-02 13:37   ` Tassilo Horn
2015-10-02 15:22     ` Artur Malabarba
2015-10-02 13:45   ` Eli Zaretskii
2015-10-02 14:14     ` Mark Oteiza
2015-10-02 14:18       ` Eli Zaretskii
2015-10-02 14:22         ` Mark Oteiza
2015-10-02 14:38           ` Eli Zaretskii
2015-10-02 16:07     ` John Wiegley
2015-10-03  0:19       ` Daniel Colascione [this message]
2015-10-03  7:22         ` Eli Zaretskii
2015-10-04  1:24           ` Daniel Colascione
2015-10-04  6:48             ` Eli Zaretskii
2015-10-02 15:13   ` Nicolas Petton

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=560F1F21.7080503@dancol.org \
    --to=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    /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).