From: Ihor Radchenko <yantar92@gmail.com>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-goto slows down org-set-property
Date: Mon, 12 Jul 2021 00:00:08 +0800 [thread overview]
Message-ID: <874kd0u9h3.fsf@localhost> (raw)
In-Reply-To: <scf1gf$96n$1@ciao.gmane.io>
Maxim Nikulin <manikulin@gmail.com> writes:
> Ihor, did you get that numbers using emacs -Q? If not, I suspect you may
> have twice more markers in the buffer than `org-refile-get-targets'
> usually generates. If my guess is correct it may be necessary to file a
> bug that org-ql or some other package abuses markers by generation to
> much of them.
With emacs -Q things are twice better, though still not good enough:
#+RESULTS[b9f5ebaf91a21d8da95b8840c70f6d9aeb2ab3ae]:
| 9.4.4 | | | |
| nm-tst | 5.572397445999999 | 38 | 1.0039881250000002 |
| org-refile-get-targets | 13.029634993 | 53 | 1.3204672779999997 |
| nm-tst | 24.142289434000002 | 25 | 0.7106094290000002 |
| org-refile-cache-clear | 0.00502349 | 0 | 0.0 |
| nm-tst | 5.043277087 | 38 | 0.8292470489999997 |
org-ql might be one of the reasons of slowdown. Without it, the nm-tst
after clearing the cache is slightly faster (was 13 sec):
#+RESULTS[e5ee2bee7b348265a19834d5ca2697618a9bf261]:
| 9.4.6 | | | |
| nm-tst | 10.106726732 | 34 | 3.0993166650000004 |
| org-refile-get-targets | 5.721277742000001 | 19 | 1.6862241439999996 |
| nm-tst | 22.056917422 | 33 | 3.000191514999999 |
| org-refile-cache-clear | 0.001498722 | 0 | 0.0 |
| nm-tst | 10.066160733 | 34 | 3.203417302 |
However, markers are also created by agendas for example. The last
result is also on fresh Emacs. Fresh Emacs tends to be faster in general.
Do you know a good way to find out all the markers associated with a buffer?
> P.S. Maybe generating of custom IDs automatically is a viable idea.
> Before I have not considered such variant believing that they would be
> noticeably longer and would have weaker associations.
Some examples of autogenerated IDs using bibtex-autokey:
du-2021-recen-studies-in-mechan-proper-e4d
Youtube-veritasium-2021-you-cant-prove-every-thats-true-346
schuh-2005-quant-insig-into-disloc-nucleat-a1d
Karl-Voit-voit-2020-draft-workf-advan-projec-manag
You can judge for yourself if it is too long or not. Also, the length
can be customised as described in bibtex-generate-autokey docstring.
Best,
Ihor
next prev parent reply other threads:[~2021-07-11 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:47 [BUG] org-goto slows down org-set-property Maxim Nikulin
2021-07-11 9:25 ` Maxim Nikulin
2021-07-11 11:49 ` Ihor Radchenko
2021-07-11 12:55 ` Maxim Nikulin
2021-07-11 14:20 ` Ihor Radchenko
2021-07-11 15:07 ` Maxim Nikulin
2021-07-11 16:00 ` Ihor Radchenko [this message]
2021-07-12 14:59 ` Maxim Nikulin
2021-07-13 14:21 ` John Kitchin
2024-07-07 12:38 ` Ihor Radchenko
2024-10-13 11:45 ` 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=874kd0u9h3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).