all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation sources
Date: Fri, 28 Sep 2007 11:36:35 -0400	[thread overview]
Message-ID: <jwvwsua24c9.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.1419.1190967231.18990.help-gnu-emacs@gnu.org

>> > Do you really claim that the size of DOC strings is of no concern at
>> > all?
>> 
>> Since they reside in the .elc files and/or the DOC file and are only
>> ever loaded into memory temporarily when they are actually consulted,
>> they take up only disk space, not main memory.  Just like the manual.

> Perhaps you should re-read th relevant sources before you make such
> assertions.  What I see there is that each displayed doc string is
> kept in memory twice, and it remains in memory until the next GC.

> So, temporary or not, the doc strings do in fact occupy memory for
> more than a split second.

Absolutely negligible.  If you add 10KB to a docstring (i.e. a *lot* more
text), that will add in the order of 10-20KB to the Emacs process on the
conditions that the user has looked at that docstring.  I.e. it will bump
the process's size from maybe 10MB to 10.02MB.  If you add 10KB to each and
every docstring ever written, then the process size will grow by about 10KB
times the number of docstring viewed in *Help*.
Absolutely negligible.


        Stefan

  parent reply	other threads:[~2007-09-28 15:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  8:04 Emacs documentation sources Dave Pawson
2007-09-26  9:23 ` Eli Zaretskii
2007-09-26 17:43 ` Sean Sieger
     [not found] ` <mailman.1329.1190828635.18990.help-gnu-emacs@gnu.org>
2007-09-26 18:07   ` Richard G Riley
2007-09-26 18:55     ` Drew Adams
2007-09-27  8:44     ` Thien-Thi Nguyen
     [not found] ` <mailman.1306.1190798609.18990.help-gnu-emacs@gnu.org>
2007-09-26 19:53   ` David Kastrup
2007-09-26 21:18     ` Eli Zaretskii
     [not found]     ` <mailman.1354.1190841494.18990.help-gnu-emacs@gnu.org>
2007-09-27  6:17       ` David Kastrup
2007-09-27  7:59         ` Eli Zaretskii
     [not found]         ` <mailma\x04n.1375.1190879967.18990.help-gnu-emacs@gnu.org>
2007-09-27 20:17           ` David Kastrup
2007-09-28  8:13             ` Eli Zaretskii
     [not found]             ` <mailman.1419.1190967231.18990.help-gnu-emacs@gnu.org>
2007-09-28 15:36               ` Stefan Monnier [this message]
2007-09-28 23:13               ` David Kastrup
2007-09-29 16:19                 ` Eli Zaretskii
     [not found]                 ` <mailman.1475.1191082767.18990.help-gnu-emacs@gnu.org>
2007-09-29 17:00                   ` David Kastrup
2007-09-29 19:09                     ` Juanma Barranquero
     [not found]         ` <mailman.1375.1190879967.18990.help-gnu-emacs@gnu.org>
2007-09-28 15:31           ` 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=jwvwsua24c9.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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.