emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Wes Hardaker <wjhns209@hardakers.net>
To: Gour <gour@atmarama.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: OBBDB(3) or org-contacts
Date: Tue, 08 Jan 2013 09:16:41 -0800	[thread overview]
Message-ID: <0lobgzh9xi.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <kcf9me$mqr$1@ger.gmane.org> (gour@atmarama.net's message of "Mon, 7 Jan 2013 21:03:24 +0100")

Gour <gour@atmarama.net> writes:

> Based on this description it seems that org-contacts is more suitable
> for the task than BBDB(3) offering ability to have custom format, easy
> editing of contacts etc., but I do wonder about scalability considering
> the following post
> (http://www.hardakers.net/code/bbdb-to-org-contacts/) where the author
> of bbdb-to-org-contacts converter wrote: "Once I point org-contacts at
> my newly generated file containing 831 records it make org-contacts
> really really slow down. I wouldn't care about the normal record
> searching process for just looking something up, but it makes loading a
> message in gnus unusable (5 second delay per message)."

FYI, I tried (again) to use org-contacts a while back and still see the
same speed problems.  It's great for small contacts, but not for large.

I think what would be needed would be to read the file and store it in
an elisp structure and then just stat() the file every time a lookup
happened and if it hasn't changed, then use the elisp or else reparse.
It's not like the data should be changing *that* much so it shouldn't
need to be reread a lot.  And it's the parsing/searching that takes too
long.

But I certainly like the org-mode format much much much better than
bbdb(3).  Which I'm still using, unfortunately.
-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/

  parent reply	other threads:[~2013-01-08 17:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 20:03 BBDB(3) or org-contacts Gour
2013-01-08  6:46 ` David Rogers
2013-01-08  7:45   ` Gour
2013-01-08 16:14 ` Daniel Clemente
2013-01-08 19:50   ` Gour
2013-01-08 21:14   ` Michael Strey
2013-01-09 14:16     ` Gour
2013-01-10  9:01       ` Michael Strey
2013-01-11 11:29     ` Karl Voit
2013-01-09 20:12   ` Nick Dokos
2013-01-09 20:28     ` Nick Dokos
2013-01-08 17:16 ` Wes Hardaker [this message]
2013-01-08 19:53   ` OBBDB(3) " Gour
2013-01-09 16:08     ` Wes Hardaker
2013-01-09 16:44       ` Gour
2013-01-13 22:04     ` Eric S Fraga
2013-01-14  8:02       ` Gour
2013-01-14  8:36       ` Gour
2013-01-14 22:14         ` Eric S Fraga
2013-01-15 10:40           ` Gour
2013-01-16  0:46             ` Eric S Fraga
2013-01-14 10:04       ` Myles English
2013-01-14 11:03         ` Gour
2013-01-14 13:04       ` Russell Adams
2013-01-14 13:27         ` Daimrod

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=0lobgzh9xi.fsf@wjh.hardakers.net \
    --to=wjhns209@hardakers.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=gour@atmarama.net \
    /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).