emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Daryl Manning <dwm+orgmode@wakatara.com>,
	Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Improving org-contacts performance (and state of development in general)
Date: Mon, 07 Sep 2020 10:26:31 +0800	[thread overview]
Message-ID: <87imcqz5ig.fsf@localhost> (raw)
In-Reply-To: <CAL9aZkvT5XqWaMTHJyree4G_Ri0Kupx_Xc1yD3-e8VPHYvngVw@mail.gmail.com>

> However, as the file and C-z notes have grown,
> performance has really started to drag. I know people have used various
> schemes (caching) etc to try to improve performance and the like, but
> updates to the file are taking a solid 5 seconds now when making major
> updates and moving tags around.

Could you provide some examples what exactly is being slow?
Maybe my WIP work on improving performance on large org files [1] might
help. 

Best,
Ihor

[1] https://www.mail-archive.com/emacs-orgmode@gnu.org/msg127740.html


Daryl Manning <dwm+orgmode@wakatara.com> writes:

> Strangely, I've come to rely over the last year on org-contacts as a
> lightweight, taggable CRM. However, as the file and C-z notes have grown,
> performance has really started to drag. I know people have used various
> schemes (caching) etc to try to improve performance and the like, but
> updates to the file are taking a solid 5 seconds now when making major
> updates and moving tags around.
>
> Is there a solid, forked branch anywhere that focuses on enhancing
> performance anywhere? I'm tempted to wade in and add features and
> improvements myself but my elisp-fu is dodgy at best (more golang these
> days.).
>
> I'd be interested in what people are doing to speed it up (and if it is
> under anything like active development for improvements. It does feel super
> handy, and feels like it just needs a performance and more modern features
> overhaul - more on interoperability and less on in-emacs interoperability.).
>
> Would love to hear what people have done overall workflow wise if they are
> using it seriously.
>
> thanks,
> Daryl.


  parent reply	other threads:[~2020-09-07  2:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 16:20 Improving org-contacts performance (and state of development in general) Daryl Manning
2020-09-06 16:27 ` Bastien
2020-09-07  8:27   ` Julien Danjou
2020-09-07 14:41     ` Bastien
2020-09-07  2:26 ` Ihor Radchenko [this message]
2020-09-07  2:52   ` Daryl Manning
2020-09-07  8:36     ` Ihor Radchenko
2020-09-07 14:43       ` Bastien
2020-09-07 15:01         ` Ihor Radchenko
2020-09-10 21:45     ` TRS-80

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=87imcqz5ig.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=dwm+orgmode@wakatara.com \
    --cc=emacs-orgmode@gnu.org \
    /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).