Re: Memory usage report

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> Date: Sat, 19 Sep 2020 23:14:52 +0800
> 
> > I think the more useful question is: are all those overlays and text
> > properties necessary?  If they are, they take the memory they are
> > supposed to take.
> 
> 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.

> > If you mean memory used by non-Lisp objects, I don't see how we could
> > produce that without having infrastructure for tracking memory
> > allocation, something that debugging malloc libraries already do.
> 
> Hmm. I am looking again at the profiler-report output. It seems to
> report the memory allocation for individual function calls (that's what
> I meant by "real" memory profiler). Do I miss something?

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.