From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Memory usage report
Date: Fri, 18 Sep 2020 11:15:02 -0400 [thread overview]
Message-ID: <jwvsgbfi0il.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zh5nfa95.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 18 Sep 2020 16:08:22 +0200")
>> Well, Lars basically said the same, but neither of you explain _why_
>> would something like that be useful. Do tell, please.
>
> If you see that you've got 13GBs worth of cons cells, you might wonder
> what variable that's holding on to them. The list of "largest
> variables", with `some-stupid-mode-I'd-forgotten-about-cache' on top
> will give you a hint.
Eli's question boils down to: can you point to a concrete case where
this would have been useful?
I have done such digging once or twice when the Lisp heap was taking
more space than I expected, but it's quite rare IME (and apparently in
Eli's as well).
So, while it might be nice to add it to `memory-usage` it's unlikely to
help in the more common cases of excessive memory use where the memory
is eaten up by objects allocated in the C part of the heap.
Stefan
next prev parent reply other threads:[~2020-09-18 15:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 19:09 Memory usage report Lars Ingebrigtsen
2020-09-17 19:19 ` Eli Zaretskii
2020-09-17 19:28 ` Lars Ingebrigtsen
2020-09-18 6:25 ` Eli Zaretskii
2020-09-18 10:51 ` Lars Ingebrigtsen
2020-09-18 11:42 ` Eli Zaretskii
2020-09-18 11:47 ` Lars Ingebrigtsen
2020-09-18 12:40 ` Eli Zaretskii
2020-09-18 12:59 ` Lars Ingebrigtsen
2020-09-18 13:17 ` Eli Zaretskii
2020-09-18 13:32 ` Ihor Radchenko
2020-09-18 14:00 ` Eli Zaretskii
2020-09-18 14:08 ` Lars Ingebrigtsen
2020-09-18 15:15 ` Stefan Monnier [this message]
2020-09-18 15:19 ` Lars Ingebrigtsen
2020-09-18 15:44 ` Eli Zaretskii
2020-09-19 14:27 ` Lars Ingebrigtsen
2020-09-19 14:48 ` Eli Zaretskii
2020-09-18 15:27 ` Eli Zaretskii
2020-09-18 14:30 ` Ihor Radchenko
2020-09-18 15:33 ` Eli Zaretskii
2020-09-18 15:37 ` Lars Ingebrigtsen
2020-09-18 15:50 ` Eli Zaretskii
2020-09-19 14:23 ` Lars Ingebrigtsen
2020-09-18 16:14 ` Ihor Radchenko
2020-09-18 19:15 ` Eli Zaretskii
2020-09-19 0:29 ` Ihor Radchenko
2020-09-19 7:51 ` Eli Zaretskii
2020-09-19 14:29 ` Lars Ingebrigtsen
2020-09-19 14:46 ` Eli Zaretskii
2020-09-19 14:54 ` Lars Ingebrigtsen
2020-09-19 15:34 ` Eli Zaretskii
2020-09-19 15:40 ` Stefan Monnier
2020-09-20 9:10 ` Lars Ingebrigtsen
2020-09-19 14:34 ` Ihor Radchenko
2020-09-19 14:53 ` Eli Zaretskii
2020-09-19 15:14 ` Ihor Radchenko
2020-09-19 15:36 ` Eli Zaretskii
2020-09-19 15:45 ` Ihor Radchenko
2020-09-19 16:05 ` Eli Zaretskii
2020-09-19 15:43 ` Stefan Monnier
2020-09-19 16:08 ` Ihor Radchenko
2020-09-19 16:18 ` Stefan Monnier
2020-09-17 19:45 ` 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
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=jwvsgbfi0il.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=yantar92@gmail.com \
/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).