From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: BASE_PURESIZE
Date: Sat, 24 Oct 2009 12:22:04 +0200 [thread overview]
Message-ID: <83ocnxf5wz.fsf@gnu.org> (raw)
In-Reply-To: <87ljj1bdyp.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Date: Sat, 24 Oct 2009 13:41:50 +0900
>
> 2. 252 KiB is not negligible, I suppose, but these days the systems
> Emacs runs on typically sport >1GB of memory, and since that's
> pure space even with multiple instances of Emacs running that is
> all that will be wasted ever.
First, we had changes committed lately that save much less than that
(FWIW, I support them). The memory size is large nowadays, but it's
all taken by programs that have even larger memory footprint.
More importantly, I think the issue here is that the numbers I
presented indicate that there's something wrong with the way we
compute PURESIZE, because on some hosts it seems to be exactly right,
while on others it wastes a lot of memory.
> 3. To save the space, dump twice, the second time using the precise
> number you can measure from the first try.
PURESIZE is a compile-time C constant, it cannot be changed at dump
time. You need to recompile.
next prev parent reply other threads:[~2009-10-24 10:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 11:00 BASE_PURESIZE Eli Zaretskii
2009-10-23 11:39 ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:10 ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:24 ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:35 ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:50 ` BASE_PURESIZE Andreas Schwab
2009-10-24 10:05 ` BASE_PURESIZE Eli Zaretskii
2009-10-24 10:37 ` BASE_PURESIZE Andreas Schwab
2009-10-24 13:18 ` BASE_PURESIZE Eli Zaretskii
2009-10-24 17:27 ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 19:01 ` BASE_PURESIZE Stefan Monnier
2009-10-25 8:24 ` BASE_PURESIZE Dan Nicolaescu
2009-10-30 1:17 ` defcustom standard-value (was: Re: BASE_PURESIZE) Dan Nicolaescu
2009-10-24 19:04 ` BASE_PURESIZE Chong Yidong
2009-10-24 19:16 ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 11:58 ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 14:24 ` BASE_PURESIZE Juanma Barranquero
2009-10-24 4:41 ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24 6:47 ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 8:24 ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24 10:22 ` Eli Zaretskii [this message]
2009-10-24 11:14 ` BASE_PURESIZE Stephen J. Turnbull
-- strict thread matches above, loose matches on Subject: below --
2006-08-05 2:16 BASE_PURESIZE Nick Roberts
2006-08-05 9:41 ` BASE_PURESIZE Eli Zaretskii
2006-08-05 16:23 ` BASE_PURESIZE Reiner Steib
2006-08-05 18:51 ` BASE_PURESIZE Richard Stallman
2006-08-05 20:07 ` BASE_PURESIZE Reiner Steib
2006-08-06 4:43 ` BASE_PURESIZE Richard Stallman
2006-08-06 9:19 ` BASE_PURESIZE Reiner Steib
2006-08-06 19:40 ` BASE_PURESIZE Reiner Steib
[not found] ` <jebqqx393g.fsf@sykes.suse.de>
2006-08-07 3:53 ` BASE_PURESIZE Eli Zaretskii
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=83ocnxf5wz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).