emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-goto slows down org-set-property
Date: Mon, 12 Jul 2021 21:59:46 +0700	[thread overview]
Message-ID: <schld2$khb$1@ciao.gmane.io> (raw)
In-Reply-To: <874kd0u9h3.fsf@localhost>

On 11/07/2021 23:00, Ihor Radchenko wrote:
> Maxim Nikulin 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:
> 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):

13.8 - 10.1 = 3.7 that is comparable with "emacs -Q" that is 5.3. So 
contribution of org-ql is not major one, but it is still significant.

> 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?

I was going to ask you, but forgot to do it. Perhaps it is impossible by 

(length org-agenda-markers)

  reply	other threads:[~2021-07-12 15:01 UTC|newest]

Thread overview: 9+ 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
2021-07-12 14:59             ` Maxim Nikulin [this message]
2021-07-13 14:21               ` John Kitchin

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:

  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='schld2$khb$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).