From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Memory usage report
Date: Sat, 19 Sep 2020 19:05:53 +0300 [thread overview]
Message-ID: <837dsp3g66.fsf@gnu.org> (raw)
In-Reply-To: <87h7rtepni.fsf@localhost> (message from Ihor Radchenko on Sat, 19 Sep 2020 23:45:37 +0800)
> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> Date: Sat, 19 Sep 2020 23:45:37 +0800
>
> >> Some of the overlays and text properties are not strictly necessary.
> >> For example, text properties are sometimes used as cache to avoid
> >> parsing text multiple times. Is the resulting speedup worth extra memory
> >> usage? It is not clear since we do not have an easy way to determine the
> >> extra memory usage.
> >
> > These are exactly the questions to ask the Org developers, I think.
>
> As an org developer, how can I know the extra memory usage by that one
> specific type of text properties?
No, you should be able to tell whether "the resulting speedup worth
extra memory usage". The memory used by a single overlay can be
easily determined by looking at the contents of an overlay object on
the C level, and similarly with text properties.
> > What that profiler counts is calls to memory-allocation functions,
> > that's all. Without being able to account for memory which was freed
> > after being allocated, these counts are useless.
>
> Got it. Then, I imagine that a simple delta of before/after running a
> function could be used to build a more useful memory report. Current GC
> report only provides the total usage, but no information on how
> individual function calls increased the memory usage.
Call garbage-collect before and after the function, and you can have
that.
> This might even be done in Elisp comparing `cons-cells-consed' and
> similar variables before/after each function call.
Not everything is exposed to Lisp. For example, how many bytes are
consumed by a cons cell.
next prev parent reply other threads:[~2020-09-19 16:05 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dsp3g66.fsf@gnu.org \
--to=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 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.