all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 6006@debbugs.gnu.org
Subject: bug#6006: recent emacs binary size increase by 800KB
Date: Thu, 22 Apr 2010 16:45:16 -0400	[thread overview]
Message-ID: <yxq1ve7rzc3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvwrvzgu75.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu\, 22 Apr 2010 15\:35\:00 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> The "data" segment size has increased between the .2 and .3 version
>> by 800KB.
> [...]
>>             * loadup.el: Setup hash-cons for pure data.
>
> Yes, this patch makes Emacs use free up a fairly large hash-table just
> before dumping, so its image is larger, with a fair amount of memory
> that's not actually used (it's still allocated to the Emacs process but
> Emacs has it registered as "free for reuse").
>
> Some of that memory can be recovered by adjusting the size of the
> pure-space (since the patch reduces the pure-space usage but didn't
> reduce the redefined size of the pure space), but not all.
>
> This said, I don't think it's a real problem since that memory is not
> really wasted (it will be used when Emacs starts to allocate), other
> than on the disk.

Part of that memory will be read from the disk at start up....
What if you allocate the hash table with a bigger size when creating
it? and maybe prefill it too.  That way there's a higher chance that
the memory will be returned to the OS when freed...







  reply	other threads:[~2010-04-22 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:13 bug#6006: recent emacs binary size increase by 800KB Dan Nicolaescu
2010-04-22 19:35 ` Stefan Monnier
2010-04-22 20:45   ` Dan Nicolaescu [this message]
2011-07-13 18:05   ` Lars Magne Ingebrigtsen

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=yxq1ve7rzc3.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=6006@debbugs.gnu.org \
    --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 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.