From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Bug: fragile org refile cache
Date: Sun, 02 May 2021 15:03:26 +0800 [thread overview]
Message-ID: <8735v5d3cx.fsf@localhost> (raw)
In-Reply-To: <87sg38j371.fsf@gmail.com>
Tim Cross <theophilusx@gmail.com> writes:
> I suspect the reason it is not done automatically is that getting that
> right for all use cases is very hard to do without adding adverse impact
> to performance. A cache which is marked as 'dirty' too often results in
> too frequent cache refresh operations, but at the same time, determining
> what changes in an org file actually invalidate the cache can be a
> process intensive operation. Allowing the user to force cache refresh
> when needed is likely a reasonable compromise.
Not really. `helm-org-ql' uses cache that is invalidated by _any_ change
in buffer + updating cache only when results are queried. Performance is
much better compared with built-in Org solutions.
Also, there is `org-element-use-cache' doing more granular cache
invalidation. You can enable it and test the performance. It is not
really degraded (except some hard-to-catch bugs existing in the
org-element-cache code).
Best,
Ihor
prev parent reply other threads:[~2021-05-02 7:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 16:09 [PATCH] Bug: fragile org refile cache Maxim Nikulin
2021-04-29 0:50 ` Samuel Wales
2021-04-29 1:29 ` Ihor Radchenko
2021-04-29 1:34 ` Samuel Wales
2021-04-29 12:45 ` Maxim Nikulin
2021-04-29 14:12 ` Ihor Radchenko
2021-04-29 15:04 ` Maxim Nikulin
2021-04-29 16:08 ` Ihor Radchenko
2021-04-29 16:51 ` Maxim Nikulin
2021-04-30 16:56 ` Maxim Nikulin
2021-05-01 14:48 ` Maxim Nikulin
2021-05-02 6:59 ` Ihor Radchenko
2021-05-04 16:55 ` Maxim Nikulin
2021-05-05 0:53 ` Ihor Radchenko
2021-04-29 13:30 ` Ihor Radchenko
2021-04-29 19:17 ` Tim Cross
2021-04-29 22:43 ` Samuel Wales
2021-05-02 7:03 ` Ihor Radchenko [this message]
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=8735v5d3cx.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@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.