From: Timothy <tecosaur@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [feature proposal] Headline caching via org-element-cache = up to 2.5x performance boost
Date: Sun, 19 Sep 2021 17:58:30 +0800 [thread overview]
Message-ID: <87a6k8esrl.fsf@gmail.com> (raw)
In-Reply-To: <87bl4p6n0m.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi Ihor,
I’ve just read through your description, and this sounds very promising! Many
thanks for going to the effort of tracking down this performance issue and
/actually making a patch to address it/.
As someone who tangles massive literate config this sounds like it could make
quite a noticeable improvement. To test this, do I need to do anything more than
just apply your patch?
> I would like to propose adding support of storing headlines in
> org-element-cache.
>
> Currently, org-element-cache only stores elements within individual
> sections. Storing headlines in cache would open various possibilities to
> improve Org performance: tag inheritance, property inheritance, category
> queries, id lookup, refile targets, agenda views, etc could all make use
> of cache.
>
> I am not proposing a mere idea, but have an actual working (WIP) code
> in: <https://github.com/yantar92/org>. Also, I am attaching a reference
> patch for org-element.el (the actual branch contains more changes).
All the best,
Timothy
p.s. I’m marking this as a patch on the tracker, since it is one :P
next prev parent reply other threads:[~2021-09-19 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 7:30 [feature proposal] Headline caching via org-element-cache = up to 2.5x performance boost Ihor Radchenko
2021-09-19 9:58 ` Timothy [this message]
2021-09-19 11:18 ` Ihor Radchenko
2021-09-19 12:39 ` Timothy
2021-09-19 12:52 ` Ihor Radchenko
2021-09-25 14:51 ` Bastien
2021-10-17 6:56 ` Ihor Radchenko
2021-10-18 5:07 ` Bastien
2021-10-17 6:57 ` Ihor Radchenko
2021-10-18 7:47 ` Bastien
2021-10-18 8:10 ` Ihor Radchenko
2021-10-18 9:25 ` Bastien
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=87a6k8esrl.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.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/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).