all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Daniel Colascione" <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: pdumper's performance
Date: Wed, 29 Aug 2018 22:14:11 -0400	[thread overview]
Message-ID: <jwv5zzsy74r.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <b6e2b55afe3c266eddad51a230c1da52.squirrel@dancol.org> (Daniel Colascione's message of "Wed, 29 Aug 2018 15:10:24 -0700")

Thanks Daniel for your prompt response.  I have some further questions, tho.

> You can see for yourself whether there's an impact. Compile an Emacs with
> support for both pdumper and unexec, dump it with unexec, and compare its
> GC performance to Emacs built without support for pdumper and also dumped
> with unexec.

I hoping to save myself the time ;-)
[ BTW, part of the reason for those questions is that I'm writing an
  article about the history of Elisp, and I'd like to understand how
  your code works so I can say something intelligent about it.
  Oh and there's not much time left before the deadline.
  Another part of course, is that I'd like to see this feature land
  on master.  ]

> As I recall, the difference is minimal.

Do you recall the tests you used and the ballpark of the difference?

>> Also I don't quite understand why this is needed: IIUC the markbits of
>> pdump'd objects are stored elsewhere, but I don't understand why that
>> needs to be the case.
> Because we don't store dumped objects in blocks and so the calculations of
> the normal locations of their mark bits would be wrong.

Hmm... OK that could explain it for conses and floats where we keep the
markbits separately from the objects in bitmaps alongside those blocs,
but you also have those <foo>_marked_p and set_<foo>_marked functions for
all other types of objects where the markbit is normally stored within
the object itself (i.e. it doesn't matter whether they're in blocks or
not).

Why did you choose to use a completely different layout for the objects
loaded from the dump?  I naively thought your code would take
cons_blocks, symbol_blocks, ... and write those blocks as-is so objects
keep the same layout, and things like mark_maybe_object don't need to be
changed at all.  I understand this would end up writing larger dumps
(since they would include some free objects), but I'd have expected it
would lead to simpler code and a smaller patch.

What am I missing?


        Stefan



  reply	other threads:[~2018-08-30  2:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 20:29 pdumper's performance Stefan Monnier
2018-08-29 22:10 ` Daniel Colascione
2018-08-30  2:14   ` Stefan Monnier [this message]
2018-08-30  5:19     ` Daniel Colascione
2018-09-04 16:26       ` Stefan Monnier
2018-09-04 16:42         ` Daniel Colascione
2018-09-04 19:30           ` Stefan Monnier
2018-09-04 19:35             ` Daniel Colascione
2018-09-04 20:58               ` Stefan Monnier
2018-09-04 21:20                 ` Daniel Colascione
2018-09-04 21:49                   ` Stefan Monnier
2018-09-04 21:33                 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv5zzsy74r.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.