emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daryl Manning <dwm+orgmode@wakatara.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Improving org-contacts performance (and state of development in general)
Date: Mon, 7 Sep 2020 00:20:35 +0800	[thread overview]
Message-ID: <CAL9aZkvT5XqWaMTHJyree4G_Ri0Kupx_Xc1yD3-e8VPHYvngVw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

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

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.


[-- Attachment #2: Type: text/html, Size: 1187 bytes --]

             reply	other threads:[~2020-09-06 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 16:20 Daryl Manning [this message]
2020-09-06 16:27 ` Improving org-contacts performance (and state of development in general) Bastien
2020-09-07  8:27   ` Julien Danjou
2020-09-07 14:41     ` Bastien
2020-09-07  2:26 ` Ihor Radchenko
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:

  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=CAL9aZkvT5XqWaMTHJyree4G_Ri0Kupx_Xc1yD3-e8VPHYvngVw@mail.gmail.com \
    --to=dwm+orgmode@wakatara.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).