unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: Time to drop the pre-dump phase in the build?
Date: Fri, 10 Jan 2014 16:05:49 -0800	[thread overview]
Message-ID: <52D08ADD.5000502@dancol.org> (raw)
In-Reply-To: <87bnzjigvc.fsf@fencepost.gnu.org>

On 01/10/2014 02:58 PM, David Kastrup wrote:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> On 01/10/2014 11:15 AM, Eric S. Raymond wrote:
>>
>>> (4) We're presently buying some startup speed at the cost of a larger
>>>       minimum working set.
>>
>> The minimum working set is zero. Modern operating systems demand-page
>> necessary information.
>
> That's a popular misconception.  The key point to note is "page" in
> demand-paging.  Unless one uses a garbage collection and topological
> sort and compaction of the memory, most of the stuff that will get paged
> in along with required data will not get accessed because it is
> unrelated.  Now a temacs dump has not seen much action with regard to
> fragmentation, but still the normal Lisp programming styles allocate and
> release enough transient memory that the image will be mixed up quite
> more than byte-compiled files will be.  Of course, if the byte-compiled
> files are small, you'll get into block waste as well.

~/edev/trunk/src
$ ps -eo pid,rss,cmd | grep '[e]macs'
31132 38516 ./temacs -Q
31136 31312 ./emacs -Q

[For emacs]
Address           Kbytes     RSS   Dirty Mode   Mapping
0000000000827000   11320   10552    8020 rw---  emacs



  reply	other threads:[~2014-01-11  0:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 19:15 Time to drop the pre-dump phase in the build? Eric S. Raymond
2014-01-10 19:49 ` Eli Zaretskii
2014-01-11  6:16   ` Paul Eggert
2014-01-11  7:17   ` Richard Stallman
2014-01-12  0:16     ` Nix
2014-01-12  3:48       ` Eli Zaretskii
2014-01-12  3:53         ` Eric S. Raymond
2014-01-11  7:17   ` Richard Stallman
2014-01-10 19:51 ` Stefan Monnier
2014-01-10 20:09   ` Eric S. Raymond
2014-01-10 20:13   ` Eli Zaretskii
2014-01-10 20:20 ` Barry Warsaw
2014-01-10 20:30   ` Eli Zaretskii
2014-01-10 21:06     ` Barry Warsaw
2014-01-10 22:19 ` Daniel Colascione
2014-01-10 22:58   ` David Kastrup
2014-01-11  0:05     ` Daniel Colascione [this message]
2014-01-10 23:23   ` Stefan Monnier
2014-01-11  0:07     ` Daniel Colascione
2014-01-11  2:58       ` Stefan Monnier
2014-01-11  3:37         ` Daniel Colascione
2014-01-11  5:13           ` Stefan Monnier
2014-01-11  5:30             ` Daniel Colascione
2014-01-11 16:14           ` Stephen J. Turnbull
2014-01-11 20:13     ` Glenn Morris

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=52D08ADD.5000502@dancol.org \
    --to=dancol@dancol.org \
    --cc=dak@gnu.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).