From: Ihor Radchenko <yantar92@posteo.net>
To: "Sebastian Wålinder" <s.walinder@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org element cache in indirect buffers
Date: Sun, 11 Jun 2023 12:51:29 +0000 [thread overview]
Message-ID: <87v8funovi.fsf@localhost> (raw)
In-Reply-To: <87o7lmb3ih.fsf@nixos.mail-host-address-is-not-set>
Sebastian Wålinder <s.walinder@gmail.com> writes:
> It appears that indirect buffers duplicate the entire org element cache from the base buffer whenever created.
Not exactly. Only link to the cache root is copied and some cache
elements may not be garbage-collected.
> Running `memory-report` indicates that each indirect buffer has the same memory blueprint.
> This becomes a massive issue with large org files.
>
> My in my 160 000 line org file, the org element cache takes 100 mb, and so each new indirect buffer consumes an additional 100 mbs of memory.
This has to be a bug in `memory-report'. Most of the cache elements will
be referenced by link and thus there should be double-counting going on somewhere.
> I also wonder if this means the caching is performed by each indirect buffer independently, and doesn't carry over.
Caching is using base buffer actually.
I guess we can explicitly set reference to the cache root to nil in
indirect buffers.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-06-11 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 12:13 Org element cache in indirect buffers Sebastian Wålinder
2023-06-11 12:51 ` Ihor Radchenko [this message]
2023-06-13 10:33 ` Ihor Radchenko
[not found] ` <CAMBKESWeHCneRwHPWkW_4-xym7OTwPEc65Z-C2WJdjcDFYwocg@mail.gmail.com>
2023-06-13 18:02 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8funovi.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=s.walinder@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/org-mode.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).